On 18 Jun, Greg Pierce wrote:
> Weird, what platform were you testing jboss on? 

Here are some of the specs:

Linux RH 6.1  2.2.12-20smp, p� en Compaq sp 700, 548 MGZ (;-)) one cpu
only
Postgresql 7.0 with jdbc7.0-1.2.jar

jboss was run with: $JAVA_HOME/bin/java -server -ms64m -mx64m -DisServer=yes -jar 
run.jar
Where java home was Sun 1.3 JDK.

Both jonas and Weblogic was run on the same plafform, but against SUN
jdk 1.2.2. (jonas with less virtuall memmory than WLS).

Peter

> 
> -----Original Message-----
> From: Peter Antman [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, June 18, 2000 4:42 PM
> To: [EMAIL PROTECTED]
> Subject: [jBoss-User] Jboss benchmark
> 
> 
> OK, this is not a benchmark, and probably not even worth considering a
> real timing, because there are a lot of different varaibles that have not
> been contrained enough. I just wanted to hear a first impression. Is this
> already known? May I have done something completly wrong, etc...
> 
> Here it comes:
> 
> I did a small timing on a bean developed with Percolator
> (http://www.percolator.org) on three different EJB servers: jboss, jonas
> and Weblogic 5.1. It is a rather small entity bean and the test was done
> from one client only. First it creates 1000 entitys, then it looks up each
> entity (in percolator mening getting all the data over in a value holder),
> then it just lookes up the same entity 1000 times.
> 
> The result? For weblogic this took about 50ms for each operation. Creating
> a bean took 50ms, looking it up 49ms. With jonas, this took about 2-3
> times longer. (184ms to create, 169ms to look up each  and 128ms to lookup
> one several times). But with jboss, this took a lot longer. It took about
> 15 times longer to create a bean compared to WLS5.1, and about 7-8 times
> longer to lookup a bean.
> 
> I have to admit, they was not even run on the same JVM, WLS was Sun 1.2.2
> for Linux and Jonas 1.3 for Linux (and I could not find a way to turn of
> all the logging in jboss), but it still sees to be a to huge different to
> really be only about runtime differenses, or am I wrong? Is there a way to
> speed up jboss? Or is this low performance a known problem?
> 
> Hope you don't take me wrong. I would really like to see jboss beeing one
> of the performance leader (it will make it a lot easier to recommend it
> then).
> 
> Greetings
> Peter
> 
> Oh, here are the numbers:
> 
> (In millis)
> Create 1000 Articles    Find 1000 Articles      Lookup 1 article 1000
> times
> Jonas  184553 (184)     169045 (169)            128174 (128)
> WLS    49886 (50)       48867                   56429
> jboss  733522 (733)     373391 (373)            379657 (379)
> 
> ------------------------------------------------------------
> Peter Antman           Technology in Media, Box 34105 100 26 Stockholm
> Systems Architect      WWW: http://www.tim.se
> Email: [EMAIL PROTECTED]        WWW: http://www.backsource.org
> Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 
> ------------------------------------------------------------
> 
> 
> 
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Problems?:           [EMAIL PROTECTED]
> 
> 
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Problems?:           [EMAIL PROTECTED]

-- 
------------------------------------------------------------
Peter Antman             Technology in Media, Box 34105 100 26 Stockholm
Systems Architect        WWW: http://www.tim.se
Email: [EMAIL PROTECTED]  WWW: http://www.backsource.org
Phone: +46-(0)8-506 381 11 Mobile: 070-675 3942 
------------------------------------------------------------



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to