[
https://issues.apache.org/jira/browse/FOR-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668469#action_12668469
]
Thorsten Scherler commented on FOR-1157:
----------------------------------------
With the dispatcher rewrite branch I find that I cannot use the 200 threads
since it will throw:
4:46:01.669 EVENT LOW ON THREADS ((100-100+4)<5) on socketliste...@0.0.0.0:8888
14:46:01.670 EVENT LOW ON THREADS ((100-100+4)<5) on
socketliste...@0.0.0.0:8888
14:46:01.808 WARN!! OUT OF THREADS: socketliste...@0.0.0.0:8888
However with this error I got 28.6 throughput for 200 thread (10 min running)
> The dispatcher rewrite is loosing throughput in jmeter tests
> ------------------------------------------------------------
>
> Key: FOR-1157
> URL: https://issues.apache.org/jira/browse/FOR-1157
> Project: Forrest
> Issue Type: Test
> Components: Plugin: internal.dispatcher
> Reporter: Thorsten Scherler
> Attachments: stress.jmx
>
>
> http://markmail.org/thread/gkp4ys65q2l7hpyy
> "The old dispatcher is around 10% faster and consumes less memory (!!!) then
> the new one. The new one is using AXIOM to create the final document which
> supposed to be faster then DOM, but it is not.
> I switch the contract processing from DOM to AXIOM to finally have SAX.
> Some sidenotes of my profiling sessions: - we use as testing ground a
> dedicated linux box which is basically a replica of
> http://juntadeandalucia.es/index.html - the side is made with cocoon 2.2 and
> "old" dispatcher cocoon 2.2 block (which is the same as we use here in
> forrest projects). - The app is running on a tomcat6 and java6. - We using
> jmeter to have an incremental test run on concurrent threads (starting with 5
> to 90 concurrent threads). "
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
