Diego,
> We are using Jonas for a client (Visa Argentina - a subsidiary of Visa
> International) as a backend for 3 Web applications (The servlet container is
> Enhydra). Jonas is running in a Sun E-240 with 1 CPU (Enhydra is running in
> 2 E-240 with 2 CPU) and we have not experienced any performance problems.
> Initially we had to tune each bean's transaction attributes to minimize
> transaction creation(we ended with a lot of Supports, some Requires, and no
> RequiresNew attributes). We also had to replicate all possible data to the
> client and had to define aggregated methods to minimize remote calls, but
> this is common to all distributed systems, not only EJB. This was our first
> EJB project, and we took most of the performance tips from
> www.theserverside.com pattern section.
>
> Now with only one EJB server (an one backup server) we are handling most
> of Visa's web application traffic. We are using SQLServer as DBMS and a
> propietary API to connect to an IBM mainframe.
> I hope that this helps to show that Jonas is fast enough.
This is a very interesting report! Indeed, I believe that JOnAS' overall speed is
quite high, but we only have that single problem with SB calling EB. JDBC
is fast enough, as CMTX-Control is (we measured out both). Our only sorrow is that we
only have a "real business speed" of about 39 to 49 entity bean loads
per second, what would be really enough for one client, but every new client cuts down
this speed, so with three client we have 13 load per client etc. A
simple calculation shows that the same server, that can server about 500 to 700
transactions (measured with a RequiresNew SB method) and with this comes near
to serve for 500 clients, now can only server 39 clients (for we have mission critical
data, processing may not need more than 1s per call, and each call has
to be a new transaction since transaction has to be commited after the call).
Do you have any idea what we can do? We also looked at TheServerSide.com, but since
most of their patterns are from "J2EE Blueprints", and our application is
mostly as told in "J2EE Blueprints", this was nothing new for us. We use ValueObject
and EB, since Blueprints tell that EB with CMP should be faster than ADO
since it can use caching.
Thak you a lot
Markus
