https://issues.apache.org/bugzilla/show_bug.cgi?id=49904

higkoo <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                URL|                            |http://hi.baidu.com/higkoo/
                   |                            |blog/item/82f97038de5fc0fcb
                   |                            |211c7b4.html
         Resolution|INVALID                     |

--- Comment #4 from higkoo <[email protected]> 2010-09-18 07:58:50 EDT ---
Recently study the use of Jmeter,unespectedly encountered the bottleneck of
test tool
Mainly because I use Jmeter to do the test of interfaces performance, the
tested server performance is better
Using LoadRunner test the maximum hits per-second nearly 3 million,nearly 40 
load machine CPU near saturation
In the same test environment to use Jmeter for Performance testing, load
machines CPU use less than 30%, while the Jmeter console CPU exhausted. 

I analyze it: 
In a GUI and without GUI testing process, do not add any listener. The results
showed very little pressure on the console, remote load machine resources were
used well again. That is say,the bottleneck is to collect and analyze data,and
the Jmeter results kept the original data. Remote load machine will immediately
upload the data to the console, this has led to Jmeter console and tested WEB
server were playing the same role. 
    The Jmeter's natural performance was inferior to the special WEB server,
resulting in the emergence of bottlenecks. 


Analysis process in details recorded to the blog: 
http://hi.baidu.com/higkoo/blog/item/82f97038de5fc0fcb211c7b4.html 

     Because the tested interface can not be external, the person who need to
reproduce the problem can install a test server Nginx server:
http://wiki.nginx.org/NginxChs  
     when compile,you should add --with-http_stub_status_module parameters on
it. 
     Then in conf/nginx.conf add such a paragraph: 

location / status ( 
    stub_status on; 
    access_log off; 
) 

    Then with http://serverip:port/status as the test address to do performance
test can be reproduced. 
    I wonder if you have the similar problems, or have any good suggestions?

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to