You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Paul Mansfield <pa...@psineteurope.com> on 2004/02/18 17:31:30 UTC
[Fwd: Apache vs JSP vs Jetspeed]
I did some performance testing using two machines which are dual
pentium4 zeons each with 4GB of memory, u320 scsi etc.
I used jakarta jmeter on one, and tested apache 1.3.28 - modjk2 - tomcat
5.0.16 - jetspeed1.4
the results are interesting. I can't say they're perfect - far from it -
because I ran each test only one unless something made me suspicious
over results (for example ensuring no developers on either machine).
-----Forwarded Message-----
Here's the results of comparing performance of our.psineteurope.com when
running different web services.
Note that apache was the front end to tomcat, tomcat runs jsps directly,
or the jetspeed webapp. The jetspeed home page was tested, as well as a
particular jetspeed portlet I wrote which simply pulls a few rows from
a mysql db (on another machine)to see how much the DB slows things down.
The following table is the page response time in milliseconds when 200
fetches are done sequentially by a varying number of parallel users. Due
to the length of the tests.
(view in fixed-width font like courier-new)
Server| Users 1 10 33 100 500
---------------------------------------------------
Apache 1 1 3 3 4
Tomcat/JSP 5 22 25 19 32
Jetspeed 73 439 1448 4709 -
Jetspeed/mysql 60 432 1465 4787* -
The results are the page response in milliseconds (1000th of a second).
I did not run a 500 "user" test against jetspeed, and truncated the 100
user jetspeed/mysql test before completion as it was taking so long, but
it still gave useful results as confirmation.
Conclusions:
For very low loads, jetspeed runs adequately, but the performance falls
off very badly as the number of parallel fetches increases. Apache, as
would be expected, sustains a heavy load without flinching, and Tomcat/JSP
seems to cope well with high loads.
The above figures are for serves running redhat7.3 and kernel 2.4.x,
without tuning anything at all.
A 20% performance improvement can be almost guaranteed with a shift from
kernel 2.4.x to 2.6.x.
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
RE: [Fwd: Apache vs JSP vs Jetspeed]
Posted by Paul Mansfield <pa...@psineteurope.com>.
On Wed, 2004-02-18 at 16:48, Mark Orciuch wrote:
> For your test, if Jetspeed is setup with db psml service, make sure you have
> the following setting in jr.props:
>
> services.PsmlManager.caching-on = true
>
> This setting is false by default. I ran some load testing recently and this
> setting made big difference for me.
thanks for that; yes, I flipped over to PSML-in-mysql and turned caching
on, it knocked about 50ms off the processing time, significant but not
enough.
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
RE: [Fwd: Apache vs JSP vs Jetspeed]
Posted by Paul Mansfield <pa...@psineteurope.com>.
On Wed, 2004-02-18 at 16:48, Mark Orciuch wrote:
> For your test, if Jetspeed is setup with db psml service, make sure you have
> the following setting in jr.props:
>
> services.PsmlManager.caching-on = true
In my settings, it was off; but we're using role-base PSML in text
files.
> This setting is false by default. I ran some load testing recently and this
> setting made big difference for me.
thanks for the tip. I will re-run some of the tests with caching on and
see if it helps.
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
RE: [Fwd: Apache vs JSP vs Jetspeed]
Posted by Mark Orciuch <ma...@ngsltd.com>.
For your test, if Jetspeed is setup with db psml service, make sure you have
the following setting in jr.props:
services.PsmlManager.caching-on = true
This setting is false by default. I ran some load testing recently and this
setting made big difference for me.
Best regards,
Mark Orciuch - morciuch@apache.org
Jakarta Jetspeed - Enterprise Portal in Java
http://jakarta.apache.org/jetspeed/
> -----Original Message-----
> From: Paul Mansfield [mailto:paul.mansfield@psineteurope.com]
> Sent: Wednesday, February 18, 2004 10:32 AM
> To: Jetspeed Users List; Jetspeed Developers List
> Subject: [Fwd: Apache vs JSP vs Jetspeed]
>
>
> I did some performance testing using two machines which are dual
> pentium4 zeons each with 4GB of memory, u320 scsi etc.
>
> I used jakarta jmeter on one, and tested apache 1.3.28 - modjk2 - tomcat
> 5.0.16 - jetspeed1.4
>
> the results are interesting. I can't say they're perfect - far from it -
> because I ran each test only one unless something made me suspicious
> over results (for example ensuring no developers on either machine).
>
> -----Forwarded Message-----
>
> Here's the results of comparing performance of our.psineteurope.com when
> running different web services.
>
> Note that apache was the front end to tomcat, tomcat runs jsps directly,
> or the jetspeed webapp. The jetspeed home page was tested, as well as a
> particular jetspeed portlet I wrote which simply pulls a few rows from
> a mysql db (on another machine)to see how much the DB slows things down.
>
> The following table is the page response time in milliseconds when 200
> fetches are done sequentially by a varying number of parallel users. Due
> to the length of the tests.
>
> (view in fixed-width font like courier-new)
>
> Server| Users 1 10 33 100 500
> ---------------------------------------------------
> Apache 1 1 3 3 4
> Tomcat/JSP 5 22 25 19 32
> Jetspeed 73 439 1448 4709 -
> Jetspeed/mysql 60 432 1465 4787* -
>
>
> The results are the page response in milliseconds (1000th of a second).
> I did not run a 500 "user" test against jetspeed, and truncated the 100
> user jetspeed/mysql test before completion as it was taking so long, but
> it still gave useful results as confirmation.
>
> Conclusions:
>
> For very low loads, jetspeed runs adequately, but the performance falls
> off very badly as the number of parallel fetches increases. Apache, as
> would be expected, sustains a heavy load without flinching, and Tomcat/JSP
> seems to cope well with high loads.
>
> The above figures are for serves running redhat7.3 and kernel 2.4.x,
> without tuning anything at all.
> A 20% performance improvement can be almost guaranteed with a shift from
> kernel 2.4.x to 2.6.x.
>
> Paul
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org