You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "David Crossley (JIRA)" <ji...@apache.org> on 2009/02/21 09:36:01 UTC

[jira] Updated: (FOR-1157) The dispatcher rewrite is losing throughput in jmeter tests

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

David Crossley updated FOR-1157:
--------------------------------

    Summary: The dispatcher rewrite is losing throughput in jmeter tests  (was: The dispatcher rewrite is loosing throughput in jmeter tests)

> The dispatcher rewrite is losing 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
>
> 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.