[ 
https://issues.apache.org/jira/browse/HTTPCORE-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oleg Kalnichevski resolved HTTPCORE-225.
----------------------------------------

    Fix Version/s:     (was: Future)
       Resolution: Won't Fix

> Improve httpcore-ab to make it possible to use it as performance test 
> framework (in JUnit)
> ------------------------------------------------------------------------------------------
>
>                 Key: HTTPCORE-225
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-225
>             Project: HttpComponents HttpCore
>          Issue Type: Improvement
>    Affects Versions: 4.1-beta1
>         Environment: All
>            Reporter: Christian Müller
>
> Hello Oleg,
> I would like to use the HttpBenchmark in the following way in my performance 
> tests (using JUnit):
> HttpBenchmark benchmark = new HttpBenchmark("http://www.google.de/";);
> benchmark.setConcurrencyLevel(10);
> benchmark.setRequests(1000);
> benchmark.setContentType("text/xml; charset=UTF-8");
> benchmark.setContent(file://mySoapRequest.xml);
> // set some other none default values
> Stats stats = benchmark.execute();
> assertEquals(0, stats.getFailureCount());
> assertEquals(0, stats.getErrorCount());
> assertTrue(stats.getAvgTime(TimeUnit.MILLISECONDS) < 200);
> assertTrue(stats.getMaxTime(TimeUnit.MILLISECONDS) < 300);
> assertTrue(stats.getThroughput(TimeUnit.SECONDS) > 20);
> assertTrue(stats.getTimePerPercent(TimeUnit.MILLISECONDS, 80) < 220); // 
> means 80% of all requests must be served in less than 220 ms 
> // some other checks
> I think this could be also useful for other people and I would ask you, if 
> you are interested that I share my further work with you?
> Regards,
> Christian

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Reply via email to