Re: Connection pool count too high?

Tech-Archive recommends: Fix windows errors by optimizing your registry

Connections stay in the same pool only if the ConnectionString are exactly
the same: the same password, the same user name...

"Dan" <Dan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6823E40C-7F4A-4E30-B5F9-E97B1C8E2D9D@xxxxxxxxxxxxxxxx
>I am trying to determine if the # of connection pools our app is using is
> 'normal'/acceptable, or if there is a problem.
>
> Our web application is all asp.net, using ADO.NET and SQL Server 2000 STD.
> The app is run on a Windows 2003 Server Web Edition and IIS 6. The
> application is broken up into 2 webs in IIS. One that contains only one
> Application Virtual Directory, and the other that is broken up into 7
> Application Virtual Directories.
>
> Every Sql Command uses the same connection string. All data access opens
> and
> closes its own connection immediately before and after the command is run.
>
> We normally have about 45 - 60 concurrent users of the app at any given
> time. And every page runs several sql commands every time they load.
>
> Below are the performance counters from both the web and sql servers that
> I
> thought were important for this research.
>
> 142 connection pools and 429 pooled connections seems very high to me. I
> know that it is hard to determine what should be 'normal' without knowing
> more about the app, but at a very high level, does this seem normal or
> would
> this indicate there is a problem?
>
>
> Connection string
> -----------------
> "User ID=<uname>;Password=<pword>;Initial Catalog=<dbname>;Data
> Source=<ip>;"
>
>
> Web Server Perf Counters
> ------------------------
> .NET CLR DATA _global_
> SqlClient Current # connection pools: 142
> SqlClient Current # pooled and nonpooled connections: 429
> SqlClient Current # pooled connections: 429
>
> Web Service
> Current Connections: 46
> Maximum Connections: 158
> Maximum Anonymous Users: 91
> Get Request/ sec: <10 - 20 avg>
>
> SQL Server Perf Counters
> ------------------------
> SQLServer:GeneralStatistics
> User Connections: 86
>
>
>


.

Relevant Pages

  • Re: Multiple worker processes for a single application in a application pool
    ... > The fact that MDAC does not have it's process does not mean that it can't ... > share connection pools across different applications. ... >>set of DLLs which run in the memory of the application.(Used MDAC many ... >>max number of connections, then how do I manage it? ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Multiple worker processes for a single application in a application pool
    ... > The fact that MDAC does not have it's process does not mean that it can't ... > share connection pools across different applications. ... >>set of DLLs which run in the memory of the application.(Used MDAC many ... >>max number of connections, then how do I manage it? ...
    (microsoft.public.inetserver.iis)
  • Re: meaning of max pool size ?
    ... maximum number of connections in a given pool (the one ... this connection string is associated with). ... across all connection pools. ... where distinct connection strings means ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: So, how do I monitor *open* connections?
    ... some code of yours called when the connections get opened or closed. ... >>> I can look at performance monitor for pools, ... >>> of the 25 pooled connections in the pool, ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: SPS 2002 SP1 install problem.
    ... pools match the one you're logging in with. ... aren't any SQL connections hanging around on the SQL database if it's not on ... > - SharePointDMAppPool which runs under local system context ... > do you suggest that I should change SharePointDMAppPool context to ...
    (microsoft.public.sharepoint.portalserver)