| Time |
S |
Nick |
Message |
| 08:54 |
|
|
Richard_2340985 joined ##friendlyjava |
| 11:32 |
|
pdurbin |
" Glassfish out of the box (as with most app servers) is optimised for development purposes. Developers want the ability to deploy and undeploy continuously, create and remove resources, debug, etc. However, this configuration is not suitable for a production system. |
| 11:32 |
|
pdurbin |
http://blog.c2b2.co.uk/2013/07/glassfish-4-performance-tuning.html |
| 11:32 |
|
pdurbin |
aditsu: is that true of Jetty too? |
| 12:01 |
|
aditsu |
pdurbin: I don't know, I've never been concerned with jetty's performance, but rather with my applications' performance |
| 12:09 |
|
aditsu |
I think only after you've optimized the *heck* out of your db queries and application code, everything is super-efficient, with no unnecessary blocking and with caching where appropriate, and still the system is under heavy usage and is not responsive enough, only then you may need to look into the server's performance |
| 12:13 |
|
aditsu |
there's some info at https://wiki.eclipse.org/Jetty/Howto/High_Load |
| 12:26 |
|
pdurbin |
sounds like out of the box jetty is fairly well tuned for production use |
| 13:02 |
|
|
pulsar_ joined ##friendlyjava |
| 15:35 |
|
|
mr_lou joined ##friendlyjava |
