Re: MaxPoolSize - Recommendations
- From: "William \(Bill\) Vaughn" <billvaRemoveThis@xxxxxxxxxx>
- Date: Fri, 1 Sep 2006 09:12:51 -0700
I'm with Mr. Beamer. I've heard of very heavily accessed sites having 25
connections in the pool. 400 is nuts. Patrice, I agree, there is some
serious problem here. Perhaps the pool is not leaking, but it's clearly not
using connections efficiently. I would chart the use of the pool via the
performance counters and see if the number stabilizes at 400 or continues to
rise--it might very well be leaking--slowly. For example, if a query
generates an exception every 1000 operations and the exception handler
bypasses the Close, it could leak slowly and not overflow for days.
Ah, if the ConnectionString changed, there would be 400 pools not 400
connections in the pool.
hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Patrice" <scribe@xxxxxxxx> wrote in message
news:u89naHdzGHA.1300@xxxxxxxxxxxxxxxxxxxxxxx
It would look rather that the connection string is not always the same....
Have you checked in SQL Server under which account those connections are
done ?
Also if you look at the max poll size (100 if I remember) and the default
pool size (don't remember) it's likely that :
- either those settings are increased for some reason by the application
- either they create mutliple pools
Anyway the idea is when you are above the default pool size you should
have less connections than users when here you have more connections than
users...
Good luck.
--
Patrice
"hrabia" <hrabia@xxxxxxxxxxxxxxxxxxxxxxxxx> a écrit dans le message de
news: 89F39CE0-350D-48D4-AA22-F0B3796E364C@xxxxxxxxxxxxxxxx
I'm testing now a third part web application (ASP.NET 2.0, MS SQL Server
2005) that seems to work properly but creates up to 400 (sic!)
connections
for average 80 concurrent users. The application is pretty
straightforward:
login, some grids with data and that's it. In my opinion (I'm an
experienced
.NET architect :) 10 concurrent connection (in a peak) should be enough
but
400 (in the pool) are very strange for me. I've informed the vendor that
the
current situations is not acceptable for me but I've got an answer that
Microsoft doesn't have any recommendations concerning "max pool size"
value,
so it can be set even to the maximum value of connections that are
allowed by
MS SQL Server (~ 32.000!). I've tried to find any official
recommendations in
msdn but I've found only sentences like "application dependent", "sense,
rational value" and so on. I have to protect my department from an
application with wrong architecture but I can't find any strong-based
arguments. Help :)!
.
- Follow-Ups:
- Re: MaxPoolSize - Recommendations
- From: Patrice
- Re: MaxPoolSize - Recommendations
- References:
- Re: MaxPoolSize - Recommendations
- From: Patrice
- Re: MaxPoolSize - Recommendations
- Prev by Date: Re: DataReader and Master-Detail
- Next by Date: Re: Creating a database on the fly
- Previous by thread: Re: MaxPoolSize - Recommendations
- Next by thread: Re: MaxPoolSize - Recommendations
- Index(es):
Relevant Pages
|