You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by "Bari, Naeem" <na...@Meridinet.com> on 2001/04/01 05:48:21 UTC
RE: cocoon performance differences betweeen Linux and Win2000
Oliver,
Its the blackdown jdk 1.1.8 that you are using. It uses
green threads, not native threads, and it is undoubtedly
the source of your pain.
If you *need* to stick to jdk 1.1.8, get IBM's version. It
is natively multithreaded and *screams*.
But upgrade to Sun's jdk 1.3 as soon as you can. I am
pretty sure it is also uses native multithreading, and
is has substantial improvements over the old version.
Trust me, switching the jdk will put the smile back on
your face :)
Regards,
naeem
p.s: Before you ask this question after switching
to the native multithreaded jdk, linux shows multiple
threads as separate processes as reported by 'ps', which
they are not. This makes it appear as if you have many
jvm processes going when you only have one with multiple
threads. Think DON'T PANIC in large friendly letters ;)
-----Original Message-----
From: Oliver Gries
To: cocoon-users@xml.apache.org
Sent: 3/31/01 8:12 AM
Subject: cocoon performance differences betweeen Linux and Win2000
Hi,
first of all I would like to point out, that I don't want to start
another
thread about Win vs. Linux. Im a very happy Linux user as well. But the
problems I got, seems however related to operating system specifics.
Let's
start.
I use an AMD K-2/300 testmachine for developing my web application based
in
cocoon. At the final stage I was a bit worry about the performance,
because
the rendering process tooks ap. 4-5 seconds, but I blamed it on the slow
testmachine. After installing it on the web hosters machine, I couldn't
really believed it, it was only half a second faster, still between 3
and 4
seconds.
So I blamed it on my stylesheet which is a bit more complex, but not
unusal. I don't do any "expensive" XSLT transformations as mentioned on
the
xalan homepage. Really just simple apply-templates stuff.
I tried to get rid of xsl:includes; xsl:imports, I tried to use xsl:key
as
often as possible and so on ... no significant change.
I currently use Cocoon 1.8, so I upgraded to 1.8.2. Now it was again 0.5
seconds faster but still about 3 seconds (for small documents, but about
6
seconds for bigger ones), but my xsp cache mechanism didn't work anymore
(... this is another problem which I wont solve with this mail). So back
to
1.8, the cache was working again.
Finally I blamed it in JServ and tried to install Tomcat 3.2.1.
I started on a Win2000 machine first.
The amazing result was, that even by running tomcat without mod_jk in
apache, the rendering time was down to 1000 milliseconds (in comparasion
to
4560 milliseconds).
I was quite happy and installed Tomcat (by simply coping the Win2000
directory with the entire sources to the linux partition and adjusting
the
conf files) on the linux partition at the same machine.
I was shocked if I saw the rendering times again increased up to 5000
milliseconds.
Under both operation systems the processor runs at 100% during a
request.
Again, I simply copied the tomcat installation from Win to linux, so
it's
defineatly the same cocoon setup.
Here are the results from the profiler:
Linux:
Tomcat Web Server/3.2.1 (JSP 1.1; Servlet 2.2; Java 1.1.8; Linux 2.2.16
x86; java.vendor=Sun Microsystems Inc., ported by the Blackdown
Java-Linux
Porting Team)
URI / Whole-request / ProducerFromFile / XSPProcessor-0 /
XSLTProcessor-1
/ HTMLFormatter / Outputting
/cocoon/jcon/workflow/webapp.xml / 16387 / 272 / 9227 / 6414 / 386 / 57
/cocoon/jcon/workflow/webapp.xml / 8480 / 226 / 88 / 7584 / 497 / 81
/cocoon/jcon/workflow/webapp.xml / 5550 / 223 / 88 / 4956 / 224 / 53
/cocoon/jcon/workflow/webapp.xml / 7447 / 226 / 87 / 6614 / 445 / 68
/cocoon/jcon/workflow/webapp.xml / 4827 / 225 / 88 / 4118 / 339 / 54
/cocoon/jcon/workflow/webapp.xml / 4885 / 229 / 89 / 4272 / 234 / 56
/cocoon/jcon/workflow/webapp.xml / 60 - - - - -
/cocoon/jcon/workflow/webapp.xml / 73 - - - - -
Win2000:
Tomcat Web Server/3.2.1 (JSP 1.1; Servlet 2.2; Java 1.1.8; Windows NT
5.0
x86; java.vendor=IBM Corporation)
URI / Whole-request / ProducerFromFile / XSPProcessor-0 /
XSLTProcessor-1
/ HTMLFormatter / Outputting
/cocoon/jcon/workflow/webapp.xml / 12518 / 240 / 6129 / 5799 / 220 / 60
/cocoon/jcon/workflow/webapp.xml / 2013 / 60 / 30 / 1743 / 150 / 20
/cocoon/jcon/workflow/webapp.xml / 2243 / 60 / 20 / 2043 / 60 / 60
/cocoon/jcon/workflow/webapp.xml / 1121 / 40 / 20 / 891 / 120 / 50
/cocoon/jcon/workflow/webapp.xml / 1803 / 30 / 21 / 1652 / 40 / 50
/cocoon/jcon/workflow/webapp.xml / 1202 / 70 / 20 / 1032 / 30 / 50
/cocoon/jcon/workflow/webapp.xml / 1141 / 30 / 20 / 1011 / 20 / 50
/cocoon/jcon/workflow/webapp.xml / 10 - - - - -
The only conclusion I get from this is, that on the linux system (
Standard
Installation Suse 7.0) the tomcat process doesn't get the same processor
power than under win2000. Or what else ... VM ??
If you leave the first 3 requests out and just start from the 3rd;
Linux
serves between 4800 and 7400 milliseconds and Win2000 between 1100 and
1800
milliseconds.
4 times faster.
I installed Tomcat and Cocoon 1.8 on an AMD Thunderbird 800 MHz / Win200
as
well. Here are the request times between 200 and 600 milliseconds.
How can I close this gab, or what am I doing wrong ??
Please, I need some help, because If I can't solve this performance
problem
I need to consider to go back to standard HTML or prerendered XML Pages
(which I really would like to avoid, because I spent quite a lot of time
of
changing this app').
Thanks in advance for any hint.
Bye
Oliver
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: Re: cocoon performance differences betweeen Linux and
Win2000
Posted by Uli Mayring <ul...@denic.de>.
On Sun, 1 Apr 2001, Matthew Cordes wrote:
> Naeem,
>
> Do you recommend Sun's jdk 1.3 over IBM's 1.3 jdk? I currently
> use IBM's and have had satisfactory results. Also all comparisons
> I've found state IBM's is generally superior speed wise.
> Have you experienced performance to the contrary?
Sun's JDK 1.3 is buggy, Netbeans doesn't run well on it. I switched to
Blackdown and now I can use Netbeans as intended. We still run Cocoon
under Sun's JDK 1.3, because no issues have surfaced there. But you might
want to keep it in the back of your head that there are bugs.
Ulrich
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: cocoon performance differences betweeen Linux and Win2000
Posted by Matthew Cordes <mc...@maine.edu>.
Naeem,
Do you recommend Sun's jdk 1.3 over IBM's 1.3 jdk? I currently
use IBM's and have had satisfactory results. Also all comparisons
I've found state IBM's is generally superior speed wise.
Have you experienced performance to the contrary?
-matt
On Sat, Mar 31, 2001 at 09:48:21PM -0600, Bari, Naeem wrote:
>
> Oliver,
>
> Its the blackdown jdk 1.1.8 that you are using. It uses
> green threads, not native threads, and it is undoubtedly
> the source of your pain.
>
> If you *need* to stick to jdk 1.1.8, get IBM's version. It
> is natively multithreaded and *screams*.
>
> But upgrade to Sun's jdk 1.3 as soon as you can. I am
> pretty sure it is also uses native multithreading, and
> is has substantial improvements over the old version.
>
> Trust me, switching the jdk will put the smile back on
> your face :)
>
> Regards,
> naeem
>
> p.s: Before you ask this question after switching
> to the native multithreaded jdk, linux shows multiple
> threads as separate processes as reported by 'ps', which
> they are not. This makes it appear as if you have many
> jvm processes going when you only have one with multiple
> threads. Think DON'T PANIC in large friendly letters ;)
>
> -----Original Message-----
> From: Oliver Gries
> To: cocoon-users@xml.apache.org
> Sent: 3/31/01 8:12 AM
> Subject: cocoon performance differences betweeen Linux and Win2000
>
> Hi,
>
> first of all I would like to point out, that I don't want to start
> another
> thread about Win vs. Linux. Im a very happy Linux user as well. But the
> problems I got, seems however related to operating system specifics.
> Let's
> start.
>
> I use an AMD K-2/300 testmachine for developing my web application based
> in
> cocoon. At the final stage I was a bit worry about the performance,
> because
> the rendering process tooks ap. 4-5 seconds, but I blamed it on the slow
>
> testmachine. After installing it on the web hosters machine, I couldn't
> really believed it, it was only half a second faster, still between 3
> and 4
> seconds.
>
> So I blamed it on my stylesheet which is a bit more complex, but not
> unusal. I don't do any "expensive" XSLT transformations as mentioned on
> the
> xalan homepage. Really just simple apply-templates stuff.
>
> I tried to get rid of xsl:includes; xsl:imports, I tried to use xsl:key
> as
> often as possible and so on ... no significant change.
>
> I currently use Cocoon 1.8, so I upgraded to 1.8.2. Now it was again 0.5
>
> seconds faster but still about 3 seconds (for small documents, but about
> 6
> seconds for bigger ones), but my xsp cache mechanism didn't work anymore
>
> (... this is another problem which I wont solve with this mail). So back
> to
> 1.8, the cache was working again.
>
> Finally I blamed it in JServ and tried to install Tomcat 3.2.1.
>
> I started on a Win2000 machine first.
>
> The amazing result was, that even by running tomcat without mod_jk in
> apache, the rendering time was down to 1000 milliseconds (in comparasion
> to
> 4560 milliseconds).
>
> I was quite happy and installed Tomcat (by simply coping the Win2000
> directory with the entire sources to the linux partition and adjusting
> the
> conf files) on the linux partition at the same machine.
>
> I was shocked if I saw the rendering times again increased up to 5000
> milliseconds.
>
> Under both operation systems the processor runs at 100% during a
> request.
>
> Again, I simply copied the tomcat installation from Win to linux, so
> it's
> defineatly the same cocoon setup.
>
> Here are the results from the profiler:
>
>
> Linux:
> Tomcat Web Server/3.2.1 (JSP 1.1; Servlet 2.2; Java 1.1.8; Linux 2.2.16
> x86; java.vendor=Sun Microsystems Inc., ported by the Blackdown
> Java-Linux
> Porting Team)
>
> URI / Whole-request / ProducerFromFile / XSPProcessor-0 /
> XSLTProcessor-1
> / HTMLFormatter / Outputting
>
> /cocoon/jcon/workflow/webapp.xml / 16387 / 272 / 9227 / 6414 / 386 / 57
> /cocoon/jcon/workflow/webapp.xml / 8480 / 226 / 88 / 7584 / 497 / 81
> /cocoon/jcon/workflow/webapp.xml / 5550 / 223 / 88 / 4956 / 224 / 53
> /cocoon/jcon/workflow/webapp.xml / 7447 / 226 / 87 / 6614 / 445 / 68
> /cocoon/jcon/workflow/webapp.xml / 4827 / 225 / 88 / 4118 / 339 / 54
> /cocoon/jcon/workflow/webapp.xml / 4885 / 229 / 89 / 4272 / 234 / 56
> /cocoon/jcon/workflow/webapp.xml / 60 - - - - -
> /cocoon/jcon/workflow/webapp.xml / 73 - - - - -
>
> Win2000:
> Tomcat Web Server/3.2.1 (JSP 1.1; Servlet 2.2; Java 1.1.8; Windows NT
> 5.0
> x86; java.vendor=IBM Corporation)
>
> URI / Whole-request / ProducerFromFile / XSPProcessor-0 /
> XSLTProcessor-1
> / HTMLFormatter / Outputting
>
> /cocoon/jcon/workflow/webapp.xml / 12518 / 240 / 6129 / 5799 / 220 / 60
> /cocoon/jcon/workflow/webapp.xml / 2013 / 60 / 30 / 1743 / 150 / 20
> /cocoon/jcon/workflow/webapp.xml / 2243 / 60 / 20 / 2043 / 60 / 60
> /cocoon/jcon/workflow/webapp.xml / 1121 / 40 / 20 / 891 / 120 / 50
> /cocoon/jcon/workflow/webapp.xml / 1803 / 30 / 21 / 1652 / 40 / 50
> /cocoon/jcon/workflow/webapp.xml / 1202 / 70 / 20 / 1032 / 30 / 50
> /cocoon/jcon/workflow/webapp.xml / 1141 / 30 / 20 / 1011 / 20 / 50
> /cocoon/jcon/workflow/webapp.xml / 10 - - - - -
>
> The only conclusion I get from this is, that on the linux system (
> Standard
> Installation Suse 7.0) the tomcat process doesn't get the same processor
>
> power than under win2000. Or what else ... VM ??
>
> If you leave the first 3 requests out and just start from the 3rd;
> Linux
> serves between 4800 and 7400 milliseconds and Win2000 between 1100 and
> 1800
> milliseconds.
>
> 4 times faster.
>
> I installed Tomcat and Cocoon 1.8 on an AMD Thunderbird 800 MHz / Win200
> as
> well. Here are the request times between 200 and 600 milliseconds.
>
> How can I close this gab, or what am I doing wrong ??
>
> Please, I need some help, because If I can't solve this performance
> problem
> I need to consider to go back to standard HTML or prerendered XML Pages
> (which I really would like to avoid, because I spent quite a lot of time
> of
> changing this app').
>
> Thanks in advance for any hint.
> Bye
> Oliver
>
>
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>