• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Piet Souris
  • Carey Brown
  • Stephan van Hulst
Bartenders:
  • Frits Walraven
  • fred rosenberger
  • salvin francis

Tomcat Performance Parameters

 
Ranch Hand
Posts: 66
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

We have web application running fine in production with 5 User in Tomcat 7, Now the user have increased from 5 to 200 users.

We need your idea/suggestions to improve the performance at tomcat 7 side however the application shouldn't crash if at a time 150 users login in to Application. What are the parameters we need to consider in Tomcat 7
when 150 user hits url at that moment.

Thanks,
Mamidi

 
Saloon Keeper
Posts: 23883
162
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There is absolutely no way to tell without more information. Tomcat doesn't have a "user limit", although it has various parameters that can be adjusted depending on the specific demands of the webapps that it is running.

We need to know what the crash information is.
 
Bartender
Posts: 1210
25
Android Python PHP C++ Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In my opinion, the best way to start analyzing this is to use a load testing tool like JMeter to load your server with (number of expected users + 20%) requests, and then collect metrics on tomcat and the server machine using performance monitoring system like collectd or munin.

Ensure that you simulate entire user flows. It's not enough to simulate 150 login attempts and then say it's fine, because the actual bottleneck is often not the authentication part but your application specific logic or database queries that run when your users are using your app.

Collect metrics, find out what bottlenecks if any - CPU, machine RAM, tomcat heap size, disk IO, database query times - are encountered, and then you can take action. Sometimes, the solution may indeed be tomcat tuning, but it's also possible the real bottlenecks are elsewhere. Database misuse is often a culprit.

No point doing general optimizations, because it's not reassuring either to you or to your management; better to analyze your system in detail, collect data, and then do focused optimization.
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic