Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Agile forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Servlet HTTP client requests

 
Ryan McClain
Ranch Hand
Posts: 145
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
1) What is the ideal methodology for handling client HTTP requests coming in for a servlet?
- Using Threads?
a) -> Is it not resource-heavy to have a million clients do a million requests at a time?
b) -> Does this only lightly affect the CPU/memory/stability on the server?
c) -> What methodology is used in real-world applications?
 
Ulf Dittmer
Rancher
Pie
Posts: 42967
73
  • Likes 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm not sure I understand the question. A servlet container does use threads, one per request. I recall reading about tests that showed that a single Tomcat instance using the NIO connector is able to handle thousands of requests per second (actually something between 10000 and 20000, if memory serves). If you need to be able to handle a million simultaneous requests that do a significant amount of work (like serious computation or accessing some other machine like a DB), you'll probably want to put in place a few hundred load-balanced machines.
 
Ryan McClain
Ranch Hand
Posts: 145
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hm, sounds interesting. Thanks
 
Paul Clapham
Sheriff
Pie
Posts: 20750
30
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In real-world applications the usual thing to do is just to use a servlet container such as Tomcat or Websphere. The situation where you have a million requests at the same time is highly unusual.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic