You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Laurent Eskenazi <le...@mail.inforama.fr> on 2000/02/21 14:19:04 UTC
Benchmark
Hi!
I've been running some little benchmarking tests this week end to see how
fast Cocoon was. I wanted to do some tests on both static and dynamic XML
documents processing and to compare these to static and dynamic HTML
documents serving, but I currently only had the static generation part
tested.
The test platform was my home computer , a K6-2 450Mhz, which 64MB of RAM, a
2GB HD operated with Linux 2.2, Apache 1.3.9, IBM JDK 1.1.8, Jserv 1.1,
Cocoon 1.6.1, Xerces 1.0.1 and James Clark's XT as the server, and my
notebook, a Pentium 233MMX with Linux 2.2, BlackDown JDK 1.2.2 RC3 and
JMeter as the client. For this test, I unloaded X Window and turned the swap
off to be sure every thing worked in memory on the server.
To compare static XML processing with static HTML serving, I used 2 sets of
files:
- A set of xml/xsl files which generate a plain HTML file with the help of
Cocoon. The generated file was about 40KB.
- One HTML file wich was in fact Cocoon's result of the above set.
So, I tested these with JMeter. Here's a sample of my results:
Static HTML serving, 1 client: 130ms / page
Static XML processing + serving, 1 client: 635ms / page
As you can see, XML processing and serving with 1 client is about 5 times
slower than a basic HTML file serving.
What do you think about this ? I find it a bit slow...Is there a way to
improve this number, and to have XML processed faster ?
Thanks !
Laurent
PS: I didn't included the files I used because I don't want to bother people
using slow connections, but I can send them to anybody wanting to try to
benchmark Cocoon as I did. I'd be very happy to compare my results with some
other's. Feel free to contact me about this: leskenazi@inforama.fr
Re[2]: Benchmark
Posted by Roman Seidl <rs...@pvl.at>.
Hello Paul,
Monday, February 21, 2000, 3:39:52 PM, you wrote:
PR> Fair enough... Fancy doing it *with* that cache for comparison? Might be
PR> interesting...
That would be very interesting - as it would show the effciency of the
caching system.
mfg
Roman Seidl
--------------------------------------------------------------------
Roman Seidl Design & Developement
--------------------------------------------------------------------
Public Voice Lab Operngasse 24, A-1040 Vienna
Tel.: +43-1-585 22 80/23 Fax: +43-1-585 22 80/99
e-mail: rse@pvl.at web: www.pvl.at
--------------------------------------------------------------------
Re: Benchmark
Posted by Paul Russell <Pa...@uea.ac.uk>.
On Mon, Feb 21, 2000 at 03:30:00PM +0100, Laurent Eskenazi wrote:
> That's right, I forgot to say I disabled the cache !
>
> I did so because this is my first step to test dynamic XML page processing
> so I don't want the cache to work there. I just wanted to see the overhead
> of XML / XSL processing over basic HTML serving.
Fair enough... Fancy doing it *with* that cache for comparison? Might be
interesting...
Paul
Re: Benchmark
Posted by Laurent Eskenazi <le...@mail.inforama.fr>.
That's right, I forgot to say I disabled the cache !
I did so because this is my first step to test dynamic XML page processing
so I don't want the cache to work there. I just wanted to see the overhead
of XML / XSL processing over basic HTML serving.
Laurent
----- Original Message -----
From: "Paul Russell" <Pa...@uea.ac.uk>
To: <co...@xml.apache.org>
Sent: lundi 21 février 2000 15:14
Subject: Re: Benchmark
> On Mon, Feb 21, 2000 at 02:19:04PM +0100, Laurent Eskenazi wrote:
> > So, I tested these with JMeter. Here's a sample of my results:
> > Static HTML serving, 1 client: 130ms / page
> > Static XML processing + serving, 1 client: 635ms / page
>
> That does seem rather slow... How are you dealing with caching?
> In my experience, cocoon is very very fast indeed when serving
> from cache (in the order of ten - twenty ms/page on my p-II 233)
> and these numbers look more typical of a fresh generation, which
> isn't really fair on cocoon.
>
> Just a thought,
>
>
> Paul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: LDAP
Posted by Stefano Mazzocchi <st...@apache.org>.
Marcello Granata wrote:
>
> I had a problem installing Cocoon 1.7. In the mailing list archive I read
> this suggestion:
> Comment out the following line in cocoon.properties:
> processor.type.ldap = org.apache.cocoon.processor.ldap.LdapProcessor
>
> I did it and now it works.
> But I'm not smart enough to understand why. Anyone can explain it to me?
the LDAP processor requires the JNDI.jar package to run and most
probably you didn't have it since Cocoon didn't ship it.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Come to the first official Apache Software Foundation Conference!
------------------------- http://ApacheCon.Com ---------------------
Re: LDAP
Posted by Bruno Melloni <br...@melloni.com>.
I was having the same problem (with Cocoon 1.7 on Win98) and tried it but
instead of working I got a different error.
Before commenting the line:
"java.lang.RuntimeException: Error creating
org.apache.cocoon.processor.ldap.LdapProcessor: make sure the needed classes
can be found in the classpath (javax/naming/directory/DirContext)"
After commenting the line (or also after putting a jndi.jar file in the
JDK/jre/lib/ext directory):
"Internal Server Error"
Suggestions?
Getting Cocoon to work on Win98 is a nightmare! This is the third or fourth
undocumented problem that I encounter. I wish they had some useful
documentation. Luckily, installing on Linux wasn't half as bad.
bruno
Mike Engelhart wrote:
> Marcello Granata wrote:
>
> > I had a problem installing Cocoon 1.7. In the mailing list archive I read
> > this suggestion:
> > Comment out the following line in cocoon.properties:
> > processor.type.ldap = org.apache.cocoon.processor.ldap.LdapProcessor
> >
> > I did it and now it works.
> > But I'm not smart enough to understand why. Anyone can explain it to me?
> >
> > Thanks marcello
> Cocoon doesn't come with Sun JNDI jar file by default because of licensing
> issues. I'm sure this will be commented out of cocoon.properties in the
> next release. If you need LDAP functionality you can get the JNDI library
> for free from http://www.javasoft.com
>
> Mike
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
Re: LDAP
Posted by Dirk-Willem van Gulik <di...@webweaving.org>.
On Thu, 2 Mar 2000, Mike Engelhart wrote:
> Cocoon doesn't come with Sun JNDI jar file by default because of licensing
> issues. I'm sure this will be commented out of cocoon.properties in the
> next release. If you need LDAP functionality you can get the JNDI library
> for free from http://www.javasoft.com
This is going to be come more and more an issue as more things get
potentially integrated with cocoon. Some #ifdef #else #endif equivalent
might be needed in conjuction with 'installed_packages.xml' :-) Or some
thing like that.
Dw
Re: LDAP
Posted by Mike Engelhart <me...@earthtrip.com>.
Marcello Granata wrote:
> I had a problem installing Cocoon 1.7. In the mailing list archive I read
> this suggestion:
> Comment out the following line in cocoon.properties:
> processor.type.ldap = org.apache.cocoon.processor.ldap.LdapProcessor
>
> I did it and now it works.
> But I'm not smart enough to understand why. Anyone can explain it to me?
>
> Thanks marcello
Cocoon doesn't come with Sun JNDI jar file by default because of licensing
issues. I'm sure this will be commented out of cocoon.properties in the
next release. If you need LDAP functionality you can get the JNDI library
for free from http://www.javasoft.com
Mike
LDAP
Posted by Marcello Granata <mg...@matrix.it>.
I had a problem installing Cocoon 1.7. In the mailing list archive I read
this suggestion:
Comment out the following line in cocoon.properties:
processor.type.ldap = org.apache.cocoon.processor.ldap.LdapProcessor
I did it and now it works.
But I'm not smart enough to understand why. Anyone can explain it to me?
Thanks marcello
Re: Benchmark
Posted by Paul Russell <Pa...@uea.ac.uk>.
On Mon, Feb 21, 2000 at 02:19:04PM +0100, Laurent Eskenazi wrote:
> So, I tested these with JMeter. Here's a sample of my results:
> Static HTML serving, 1 client: 130ms / page
> Static XML processing + serving, 1 client: 635ms / page
That does seem rather slow... How are you dealing with caching?
In my experience, cocoon is very very fast indeed when serving
from cache (in the order of ten - twenty ms/page on my p-II 233)
and these numbers look more typical of a fresh generation, which
isn't really fair on cocoon.
Just a thought,
Paul
Re: Cache and producer
Posted by Ross Burton <bu...@dcs.kcl.ac.uk>.
> I have written a producer which generates static XML (like the
> DummyProducer). It works fine - but after the first call the resulting
page
> is cached. When I then change the XML data and recompile the producer I
> still get the old output.
>
> I have set
>
> cache = org.apache.cocoon.cache.NoCache
>
> in cocoon.properties - but this does not help. Neither does restarting
> Apache 1.3.9 and Jserv 1.1. The only way to get the new output seems to be
> by rebooting my system (Win98).
Are you sure it's not the browser caching? Most browsers only check the
file from the server for updates once every session, change this to every
time and it should work fine. I had this problem in Netscape (I don't any
more because Cocoon has broken again!)
Ross Burton
"Thirty days with a crew of viral masochists and a ship that thinks it's a
cuddly toy."
- Diziet Embless Sma, 'Use of Weapons' - Iain M. Banks
Slipstream: http://come.to/slipstream
The Culture: http://come.to/theculture
ICQ: 5167146
AW: AW: Cache and producer
Posted by Matthew Langham <ml...@sundn.de>.
Thanks for all the tips.
The problem was that the Java runtime was still in memory after I stopped
Apache. So my producer remained in memory even though I had changed it and
stopped Apache+JServ.
I tried apache -k shutdown but this didnt help (Win98)
>
> >>
> Sounds like a browser cache problem. What browser are you using?
> <<
>
> I have tested with both Communicator and IE. Happens on both (even
> restarting browser - clearing cache etc.).
>
> After altering my producer - the only way I can get the new output to show
> up is to reboot my system. Perhaps there is some configuration of Jserv I
> should be looking at?
Matthew
--
CeBIT Hannover 24.2.-1.3.2000 Halle 18/EG Stand A24/39
=================================================================
Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
Tel: +49-5251-1581-30 [mlangham@sundn.de - http://www.sundn.de]
=================================================================
Re: AW: Cache and producer
Posted by Stefano Mazzocchi <st...@apache.org>.
Matthew Langham wrote:
>
> >>
> Sounds like a browser cache problem. What browser are you using?
> <<
>
> I have tested with both Communicator and IE. Happens on both (even
> restarting browser - clearing cache etc.).
>
> After altering my producer - the only way I can get the new output to show
> up is to reboot my system. Perhaps there is some configuration of Jserv I
> should be looking at?
I've never seen such a problem.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Come to the first official Apache Software Foundation Conference!
------------------------- http://ApacheCon.Com ---------------------
AW: Cache and producer
Posted by Matthew Langham <ml...@sundn.de>.
>>
Sounds like a browser cache problem. What browser are you using?
<<
I have tested with both Communicator and IE. Happens on both (even
restarting browser - clearing cache etc.).
After altering my producer - the only way I can get the new output to show
up is to reboot my system. Perhaps there is some configuration of Jserv I
should be looking at?
Matthew
>>>
Von: Stefano Mazzocchi [mailto:stefano@apache.org]
>
> I have written a producer which generates static XML (like the
> DummyProducer). It works fine - but after the first call the resulting
page
> is cached. When I then change the XML data and recompile the producer I
> still get the old output.
>
> I have set
>
> cache = org.apache.cocoon.cache.NoCache
>
> in cocoon.properties - but this does not help. Neither does restarting
> Apache 1.3.9 and Jserv 1.1. The only way to get the new output seems to be
> by rebooting my system (Win98).
>
> Ideas?
Sounds like a browser cache problem. What browser are you using?
<<<
--
CeBIT Hannover 24.2.-1.3.2000 Halle 18/EG Stand A24/39
=================================================================
Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
Tel: +49-5251-1581-30 [mlangham@sundn.de - http://www.sundn.de]
=================================================================
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Come to the first official Apache Software Foundation Conference!
------------------------- http://ApacheCon.Com ---------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org
XSL with Cocoon - getting started!
Posted by Matthew Langham <ml...@sundn.de>.
I now have Cocoon up and running with my own producer. Fine. Now I need to
quickly knock up some XSL/XML stuff to be able to show the whole thing off
to management. I would like to be able to convert given XML to HTML and WML.
Am I stuck to authoring the XSL stuff by hand - or is there an easier way to
get some stylesheets set up for my XML data?
Matthew
--
CeBIT Hannover 24.2.-1.3.2000 Halle 18/EG Stand A24/39
=================================================================
Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
Tel: +49-5251-1581-30 [mlangham@sundn.de - http://www.sundn.de]
=================================================================
Re: Cache and producer
Posted by Stefano Mazzocchi <st...@apache.org>.
Matthew Langham wrote:
>
> I have written a producer which generates static XML (like the
> DummyProducer). It works fine - but after the first call the resulting page
> is cached. When I then change the XML data and recompile the producer I
> still get the old output.
>
> I have set
>
> cache = org.apache.cocoon.cache.NoCache
>
> in cocoon.properties - but this does not help. Neither does restarting
> Apache 1.3.9 and Jserv 1.1. The only way to get the new output seems to be
> by rebooting my system (Win98).
>
> Ideas?
Sounds like a browser cache problem. What browser are you using?
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
Come to the first official Apache Software Foundation Conference!
------------------------- http://ApacheCon.Com ---------------------
Cache and producer
Posted by Matthew Langham <ml...@sundn.de>.
I have written a producer which generates static XML (like the
DummyProducer). It works fine - but after the first call the resulting page
is cached. When I then change the XML data and recompile the producer I
still get the old output.
I have set
cache = org.apache.cocoon.cache.NoCache
in cocoon.properties - but this does not help. Neither does restarting
Apache 1.3.9 and Jserv 1.1. The only way to get the new output seems to be
by rebooting my system (Win98).
Ideas?
Thanks
Matthew
--
CeBIT Hannover 24.2.-1.3.2000 Halle 18/EG Stand A24/39
=================================================================
Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
Tel: +49-5251-1581-30 [mlangham@sundn.de - http://www.sundn.de]
=================================================================
Re: Benchmark
Posted by Mike Engelhart <me...@earthtrip.com>.
Darren Scott wrote:
> Hi,
>
> Some people have mentioned running Cocoon with Jigsaw. Have any
> performance benefits been noted from cutting out the apjv11 protocol?
> (my apologies if 'apjv11' isn't correct, but i'm sure you all know what
> I mean).
>
> Also, has anybody tried TowerJ?
>
> Just some random thoughts...
>
> Darren Scott
> Technical Director
> bluecheese.co.uk
Apjv11 and apjv12 are Apache JServ specific. There are dozens of other
servlet engines that don't use ApJv11 or ApJv12 and don't incur that
overhead (although depending on what method they use to communicate with the
http server they may have different overhead issues). Jigsaw is a pretty
speedy web server although it's fairly complex to setup in my opinion.
Most of the performance issues with Cocoon have nothing to do with what
servlet setup you have. It's just the complexity of the processing and
having to load in possibly multiple stylesheets and XML documents and have
them all be processed by XSLT.
Mike
Re: Benchmark
Posted by Darren Scott <ds...@bluecheese.co.uk>.
Hi,
Some people have mentioned running Cocoon with Jigsaw. Have any
performance benefits been noted from cutting out the apjv11 protocol?
(my apologies if 'apjv11' isn't correct, but i'm sure you all know what
I mean).
Also, has anybody tried TowerJ?
Just some random thoughts...
Darren Scott
Technical Director
bluecheese.co.uk
Re: Benchmark
Posted by Laurent Eskenazi <le...@mail.inforama.fr>.
> For strictly un-cached dynamic pages, that's actually quite a bit faster
> than I'd have expected from cocoon. Cocoon has to read and parse two
> files, run a complex processor, and then spit output; static apache just
> has to read a file and spit output. I think a 4x differential is
> astonishing and probably indicates that you've got a simple stylesheet. :)
Right ! Very simple.
> If you're hell-bent on speed though, the best way to speed it up at this
> point would be to turn on the cache and then go help Pier with cocoon2
> (which uses SAX internally and should help a bit).
I didn't see any difference on dynamic pages with the cache on...does it
really help ?
What's the status of Cocoon 2...is there a timeframe for its developpement ?
Unfortunately, I'm quite busy these days and I won't be able to work on it
=+( Good luck to him anyway!
Laurent
Re: Benchmark
Posted by Thomas Yip <ty...@yahoo.com>.
> If you're hell-bent on speed though, the best way to speed it up at this
> point would be to turn on the cache and then go help Pier with cocoon2
> (which uses SAX internally and should help a bit).
Well, I am interested to have a sneak peek of cocoon2, could anyone
tell me where can I find that? I don't see any link in xml.apache.org.......
Re: Benchmark
Posted by Donald Ball <ba...@webslingerZ.com>.
On Mon, 21 Feb 2000, Laurent Eskenazi wrote:
> I've been running some little benchmarking tests this week end to see how
> fast Cocoon was. I wanted to do some tests on both static and dynamic XML
> documents processing and to compare these to static and dynamic HTML
> documents serving, but I currently only had the static generation part
> tested.
>
> The test platform was my home computer , a K6-2 450Mhz, which 64MB of RAM, a
> 2GB HD operated with Linux 2.2, Apache 1.3.9, IBM JDK 1.1.8, Jserv 1.1,
> Cocoon 1.6.1, Xerces 1.0.1 and James Clark's XT as the server, and my
> notebook, a Pentium 233MMX with Linux 2.2, BlackDown JDK 1.2.2 RC3 and
> JMeter as the client. For this test, I unloaded X Window and turned the swap
> off to be sure every thing worked in memory on the server.
>
> To compare static XML processing with static HTML serving, I used 2 sets of
> files:
> - A set of xml/xsl files which generate a plain HTML file with the help of
> Cocoon. The generated file was about 40KB.
> - One HTML file wich was in fact Cocoon's result of the above set.
>
> So, I tested these with JMeter. Here's a sample of my results:
> Static HTML serving, 1 client: 130ms / page
> Static XML processing + serving, 1 client: 635ms / page
>
> As you can see, XML processing and serving with 1 client is about 5 times
> slower than a basic HTML file serving.
>
> What do you think about this ? I find it a bit slow...Is there a way to
> improve this number, and to have XML processed faster ?
For strictly un-cached dynamic pages, that's actually quite a bit faster
than I'd have expected from cocoon. Cocoon has to read and parse two
files, run a complex processor, and then spit output; static apache just
has to read a file and spit output. I think a 4x differential is
astonishing and probably indicates that you've got a simple stylesheet. :)
If you're hell-bent on speed though, the best way to speed it up at this
point would be to turn on the cache and then go help Pier with cocoon2
(which uses SAX internally and should help a bit).
- donald
RE: Benchmark
Posted by John Cyriac <jc...@hcltech.com>.
hi ,
this is great job. please send the details
-john
-----Original Message-----
From: Laurent Eskenazi [mailto:leskenazi@mail.inforama.fr]
Sent: Monday, February 21, 2000 5:19 AM
To: Cocoon
Subject: Benchmark
Hi!
I've been running some little benchmarking tests this week end to see how
fast Cocoon was. I wanted to do some tests on both static and dynamic XML
documents processing and to compare these to static and dynamic HTML
documents serving, but I currently only had the static generation part
tested.
The test platform was my home computer , a K6-2 450Mhz, which 64MB of RAM, a
2GB HD operated with Linux 2.2, Apache 1.3.9, IBM JDK 1.1.8, Jserv 1.1,
Cocoon 1.6.1, Xerces 1.0.1 and James Clark's XT as the server, and my
notebook, a Pentium 233MMX with Linux 2.2, BlackDown JDK 1.2.2 RC3 and
JMeter as the client. For this test, I unloaded X Window and turned the swap
off to be sure every thing worked in memory on the server.
To compare static XML processing with static HTML serving, I used 2 sets of
files:
- A set of xml/xsl files which generate a plain HTML file with the help of
Cocoon. The generated file was about 40KB.
- One HTML file wich was in fact Cocoon's result of the above set.
So, I tested these with JMeter. Here's a sample of my results:
Static HTML serving, 1 client: 130ms / page
Static XML processing + serving, 1 client: 635ms / page
As you can see, XML processing and serving with 1 client is about 5 times
slower than a basic HTML file serving.
What do you think about this ? I find it a bit slow...Is there a way to
improve this number, and to have XML processed faster ?
Thanks !
Laurent
PS: I didn't included the files I used because I don't want to bother people
using slow connections, but I can send them to anybody wanting to try to
benchmark Cocoon as I did. I'd be very happy to compare my results with some
other's. Feel free to contact me about this: leskenazi@inforama.fr
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org