cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylvain.wal...@anyware-tech.com>
Subject Re: Who needs 386% speed up?
Date Mon, 28 Jan 2002 13:33:33 GMT
Michael Homeijer wrote:

>
>>-----Original Message-----
>>From: Sylvain Wallez [mailto:sylvain.wallez@anyware-tech.com]
>>Sent: maandag 28 januari 2002 10:11
>>To: cocoon-dev@xml.apache.org
>>Subject: Re: Who needs 386% speed up?
>>
>>
>>Torsten Curdt wrote:
>>
>>>On Sun, 27 Jan 2002, Vadim Gritsenko wrote:
>>>
>>>>Hi,
>>>>
>>>>While playing with OptimizeIt, I found quite interesting 
>>>>
>>piece of code
>>
>>>>in Xalan code, class org.apache.xml.utils.DefaultErrorHandler:
>>>>
><snip>
>
>>>>PPS XSPs *are* fast. XSL is slow :-|
>>>>
>>>...but people say XSPs are not skaling very good. AFAIR 
>>>
>>(vaguely) Berin
>>
>>>tracked this down (also with optimizeIt) and it was a 
>>>
>>classloader issue.
>>
>>>Berin, is this right? Please correct me if I am wrong... I guess this
>>>raised the monitoring thread...
>>>
>>... or is this bad scalability a past myth ? I refactored 
>>ServerPagesGenerator at the beginning of december to make the 
>>document-completion stuff faster and optional (disabled by default). 
>>This was using a LinkedList to keep track of the open XML elements.
>>
>>For more info, see 
>>http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=100739488123738&w=2
>>
>
>I am one of the people that were confronted with the scalability problem on
>a project. We still have a large site for a customer running on Cocoon 1
>because it scaled better.
>
>The migration project was put on hold because we could only get the site
>performing about 10% better and scalability was a problem. Unfortunately I
>have only been part of the project for the Cocoon 1 to 2 migration and was
>not able to test the following things:
>- the new serverpages generator with the optional document-completion stuff.
>- using the classes generated by XSP directly as a generator (this could
>show if there is a classloading problem).
>
>I don't think you can call scalability 'a past myth' until Cocoon 2 has had
>some real scalability tests, either in a real-world project or in some
>testcase. 
>
>Michael
>
You're right in saying that XSP (and more generally Cocoon) needs some 
formal scalability and test benchmarks. What I was meaning is that a lot 
of work has been done to speed up the XSP engine and that the bad 
experiences people may have encoutered in the past should be confronted 
with today's engine.

I'd be very thankful if someone had the required time and competence to 
set up and include in the CVS a JMeter test suite that would allow us to 
compare objectively two versions of Cocoon.

Also, can someone point me to these speed-related classloading issues ?

Cheers,
Sylvain

-- 
Sylvain Wallez
Anyware Technologies - http://www.anyware-tech.com




---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message