Post reply

Connection pool size

  • November 21, 2005 at 7:21 am

    #110938

    Hello,

    I Have a question regarding the connection pool size:

    I have a server application above SQL Server. When I'm trying to handle many clients (200 users) I encountered a timeout when trying to open a connection: “Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached.”

    Further info: I'm using the default connection pool size and default timeout periods.

    My Questions:

    1. What is the size of the connection pool that I need to use? Should I use the default size?

    2. If I should change the connection pool size, how do you determine the size to use? What are the affecting parameters? Should I manage it at runtime?

    3. How can I determine the number of users per given hardware (for example, 1 CPU P4 3 GHz, 1-2 GB RAM)?

    Thanks a lot...

  • November 21, 2005 at 11:40 am

    #605029

    1)Haven't really got that situation myself, but it can be because connections aren't closed as quickly as possible after their use.

    http://www.15seconds.com/issue/040830.htm

    3) It all depends wath the server will do, how heavy the stress will be...

    There is a difference between 200 users each querying an occasional record versus 200 users generating reports using bad query practises.

    I would recommend at least 2gb ram (since it is quite cheap nowadays) unless for occasional use.

     

  • November 22, 2005 at 10:02 am

    #605282

    A SQL Server can choke on a 20 conenction load with a single processor (let alone 200 !). In this day and age hardware is cheap. Our minimum server spec is a Dual Xeon 2.8+ Gh CPU server with 2 Gb of RAM.

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply