Received: (qmail 41356 invoked by uid 501); 9 Apr 2001 07:08:16 -0000 Message-Id: <20010409070816.41355.qmail@apache.org> Date: 9 Apr 2001 07:08:16 -0000 From: zhanghong Reply-To: hong_zhang@nj.trendmicro.com To: submit@bugz.apache.org Subject: performance is too low under heavy load X-Send-Pr-Version: 3.110 >Number: 7544 >Category: mod_proxy >Synopsis: performance is too low under heavy load >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Apr 09 00:10:00 PDT 2001 >Closed-Date: Sun Apr 15 11:29:04 PDT 2001 >Last-Modified: Sun Apr 15 11:29:04 PDT 2001 >Originator: hong_zhang@nj.trendmicro.com >Release: 1.3.12 >Organization: >Environment: windowsNT, sp6 >Description: under 500 concurrant requests, the performance becomes to slowly, but at this time the cpu usage is just 45%, and memory left much, I want to know is there any soluction to progress the performance. >How-To-Repeat: >Fix: I want to whether we can modify the windows registry to get high performance. >Release-Note: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: slive State-Changed-When: Sun Apr 15 11:29:04 PDT 2001 State-Changed-Why: Sorry, but we can only handle bug reports in the bug database. You will probably have more luck with a question like this in news:comp.infosystems.www.servers.ms-windows Thanks for using Apache! >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]