• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

connection pool properties

 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have a web application that has potential to be used by about 250-300 people simultaneously. What do you suggest setting the Maximum Connections property in WAS6.0?
 
author and cow tipper
Posts: 5009
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Why not set it to 250-300? That way you'll always have enough connections.

Okay, that's a snide answer. But seriously, why even worry about setting an upper limit?

Well, the answer has less to do with your users, and more do do with workload and througput. The real question is, how much can your database handle. If you database can handle 300 connections, put it to 300. Does performance degrate before or after 300? When do wait times become unacceptable. Does that happen after 10 connections or after 30 connections?

My idea about connection pools is that I limit them to the point where creating the nth one no longer brings any performance gain. After that point, you either limit the number of connections, or increase your database capacity.

What about licenses? Are you capped by licenses?

These are all some of the redirects I'm trying to give you to avoid the entire topic.

Here's a little something on my website that provides more information about configuring a WebSphere 5 or 6.1 connection pool or datasource:

http://www.technicalfacilitation.com/get.php?link=pooling

Enjoy!

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

If 300 is number of concurrent users, then the number of connections should be 300, so that all users should be able to access the application. But if the number of users (300) are total users then the number of connections should be less. If excessive connctions are maintianed by the server, performance would be an issue..
Check out the following link for more information and further pointers.
http://publib.boulder.ibm.com/infocenter/wasinfo/v5r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/cdat_conpool.html

Regards,
Roshani
 
Kathy Brodeur
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
thanks everyone- this information helps me. I just wanted to get an idea....I wasn't sure if 200 connections would be ridiculous or not. thanks for your input.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic