EJB Test Results
Configuration
Hardware Compaq 7940
CPU AMD Athlon 800MHz
RAM 256M
OS Windows 2000
JDK Vendor/Version Sun 1.3
EJB Server jboss 2.0 final
Servlet Engine tomcat 3.2b7
DB hypersonic
Results
Test Description Number of concurrent clients
1 10 50 100
Simple Entity Bean creation (optimized) 5.337 5.598 7.401 8.012
Simple Entity Bean creation (serialized) 11.286 10.615 13.64 12.588
Complex Entity Bean creation (optimized) 11.947 15.412 18.267 22.432
Complex Entity Bean creation (serialized) 26.368 27.149 31.405 38.696
Read-only call on an entity bean (optimized) 7.15 7.02 7.1 7.171
Read-only call on an entity bean (serialized) 8.682 8.553 9.494 8.863
Write call to entity (optimized) 20.91 21.211 22.112 22.112
Write call to entity (serialized) 30.814 29.082 30.284 30.584
Call to stateful session (optimized) 0.3 0.341 0.36 0.381
Call to stateless session (optimized) 0.28 0.29 0.33 0.361
(times are in ms, simple entity carry an int, complex a string with 1000
chars) tuned updates turned off
just FYI we will post real data soon
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Stefan R�per
|Sent: Tuesday, November 28, 2000 9:15 AM
|To: Jboss-User (E-Mail)
|Subject: [jBoss-User] jBoss Performance - Benchmark
|
|
|Hi folks,
|
|i have tested now also orionserver with my little app.
|The results are a little bit frustrating for the jBoss configs,
|can anybody please explain the big difference for EJB invocation ?
|
|Server Configuration:
|Pentium Pro 200MHz
|RAM 64 MB
|IDE Drive
|Red Hat Linux 7.0
|
|Tomcat 3.2b7 / Jboss 2.0 Final from binary download section.
|Jetty 3.0.0 RC 6 / jBoss 2.1 PRE from binary download section.
|Orionserver 1.3.8
|
|Client Configuration:
|Pentium III 400 MHz
|RAM 128 Mb
|IDE Drive
|MS Windows 2000 Server
|
|MS Web Application Stress Tool 1.1.293.1
|All Tests with 64 Threads, 2 min Duration, 30 sec Warmup and Cooldown
|Protokoll HTTP/1.1 used.
|
|Network 100Mbits
|
| jBoss / jBoss /
| Apache Tomcat Jetty Orion
|-------------------------------------------------------------------
|--------------------
|HTML 401.84 76.86 60.51 660.47
|Requests/sec
| 157.38 827.82 937.71 83.13 Avg.
|TTFB in ms (Time to first Byte)
|
|Servlet -- 13.59 12.27 13.77
|Request/sec
| 4705.21 5224.73 4647.19 Avg. TTFB in ms
|
|EJB -- 5.00 6.00 77.07 Req/sec
| 13595.61 11425.08 817.82
|Avg. TTFB in ms
|
|
|The HTML Page was very small, only 163 Bytes, no Images or further
|references.
|The 660.47 Req/sec with Orionserver may be too small, my Client
|shows over 90% CPU during the test.
|
|The Servlet does an database query over the Network on a
|postgresql database, resulting page is 365 Bytes.
|I do an open database, query, close database in doGet, so driver
|performance counts.
|
|The EJB Test is constructed by an servlet, a session bean and
|entity beans with CMP on the same database and same table as used
|for the servlet test.
|The resulting page from servlet and EJB test is identical (365 Bytes).
|
|
|Stefan Roeper
|
|SoftWork EDV GmbH
|Robert-Bosch-Str.12, 30989 Gehrden
|Tel: 05108 / 6402 -11 Fax: -29 Mobil: 0177 / 277 48 71
|http://www.softwork-edv.de
|mailto:[EMAIL PROTECTED]
|
|
|-----Urspr�ngliche Nachricht-----
|Von: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]Im Auftrag von Julian Gosnell
|Gesendet: Donnerstag, 16. November 2000 11:16
|An: jBoss
|Cc: [EMAIL PROTECTED]
|Betreff: Re: [jBoss-User] Jetty vs Tomcat
|
|
|Jetty has a super-fast implementation to serve any
|kind of page - static, dynamic (CGI, Servlet, JSP,
|WebApp). Furthermore, because no arbitrary distinction
|between different content types has to be made, and
|because the http server and servlet container are so
|tightly integrated Jetty can be extremely efficient.
|
|Just my penniesworth,
|
|Jules
|
|
|--- Bill Pfeiffer <[EMAIL PROTECTED]> wrote: >
|If your plan is to just use your servlet container
|> to serve up http, why not use tomcat without apache.
|> The benefit of running apache is that it serves
|> static pages fast (I'm sure there are others). If
|> everything is going to come out of the servlet
|> container, however, just set tomcat to listen on
|> port 80.
|>
|> Unless jetty has some super fast http implementation
|> to serve up static pages, I think your loking at 6
|> of one and half a dozen of the other.
|>
|> Bill Pfeiffer
|>
|> ----- Original Message -----
|> From: Michael G. Drew
|> To: jBoss
|> Sent: Wednesday, November 15, 2000 4:26 PM
|> Subject: [jBoss-User] Jetty vs Tomcat
|>
|>
|> I would like to design my web apps so that I can
|> access them directy through a normal http url. ie:
|> www.myserver.com/myapp NOT:
|> www.myserver.com:8080/myapp. I know I can do this
|> by getting tomcat and apache working together, but
|> when I introduce jBoss in the mix, I haven't been
|> able to get the AJP12 communication working that is
|> necessary for apache to work with tomcat.
|>
|> The way I see it there are two options:
|>
|> Use jBoss/tomcat/apache: must figure
|> out AJP12 stuff
|>
|> might be a bit slower (according to list)
|>
|> Use jBoss/Jetty: since Jetty is both a
|> Servlet container and Http server, I believe by
|> integrating it into jBoss, I'll be able to have all
|> three components (servlet, http, ejb) all working
|> together AND be inVM. I'm assuming this should be
|> much faster than the jBoss/tomcat/apache approach.
|> I'm also assuming that I might be able to get my
|> url's working again with this approach.
|>
|> Could someone please comment on the
|> advantages/disadvantages of these two approaches and
|> let me know if I've missed the mark on anything.
|> Many thanks as usual!
|>
|>
|> Michael G. Drew
|> Kishwaukee College
|> Interface Programmer
|> [EMAIL PROTECTED]
|> (815) 825-2086 ext 595
|>
|>
|
|
|__________________________________________________
|Do You Yahoo!?
|Yahoo! Calendar - Get organized for the holidays!
|http://calendar.yahoo.com/
|
|
|--
|--------------------------------------------------------------
|To subscribe: [EMAIL PROTECTED]
|To unsubscribe: [EMAIL PROTECTED]
|Problems?: [EMAIL PROTECTED]
|Nn�n������N�rz�z~��vr�z����
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
