tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Goldsmith <>
Subject Re: TomEE performance
Date Mon, 23 Jan 2017 15:10:05 GMT
Romain is correct since there are many vectors involved. I have a simple
geofencing service that scales out to over 1m requests a day and it runs on
a server with other apps. I have another app that is more sophisticated,
but leverages JCache and is on the same server. Only two VMs (2 vCPUs, 8G
RAM) are utilized to handle 10K+ live users at a time. In my experience
TomEE scales plenty well, but you should be prepared to add another VM as
needed behind the LB.

Easier to decommission and extra VM than have the app fail and have to spin
another up and configure.

On Mon, Jan 23, 2017 at 6:36 AM, David Villacampa Rodriguez <> wrote:

> Hi all,
> We would like to know, before launch the load performance test. We are
> still in solution analysis time:
> Which is the maximum number of concurrent users or clients supported by
> TomEE server?
> Context:
> Application Web functionalities: login against LDAP plus 2 screens for
> showing few data from the database.
> Hardware = 2 CPU, RAM 16GB, HDD 250GB
> Many thanks in advance, regards,
> David
> ________________________________
> Este correo y la información contenida o adjunta al mismo es privada y
> confidencial y va dirigida exclusivamente a su destinatario. everis informa
> a quien pueda haber recibido este correo por error que contiene información
> confidencial cuyo uso, copia, reproducción o distribución está expresamente
> prohibida. Si no es Vd. el destinatario del mismo y recibe este correo por
> error, le rogamos lo ponga en conocimiento del emisor y proceda a su
> eliminación sin copiarlo, imprimirlo o utilizarlo de ningún modo.
> This message and the information contained in or attached to it are
> private and confidential and intended exclusively for the addressee. everis
> informs to whom it may receive it in error that it contains privileged
> information and its use, copy, reproduction or distribution is prohibited.
> If you are not an intended recipient of this E-mail, please notify the
> sender, delete it and do not read, act upon, print, disclose, copy, retain
> or redistribute any portion of this E-mail.

Steven P. Goldsmith

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message