Hi folks,

We are doing some performance testing on a tiered app - IIS>WebSphere>SQL2005.

We are running some scripts to emulate multiple users interacting with the
app. IIS is a front end only - no apps installed on IIS other than Websphere
plugin.
As we move above 10 concurrent users we lose around 50% of connections with
the following HTTPErr entries:

Connection_Dropped DefaultAppPool
Connection_Abandoned_By_AppPool Defaultapppool

No Windows Event errors are occuring. At the test client we receive a
"Socket error on port 80".

We are running some perf counters across the board and some other testing to
identify bottlenecks, but I am looking for some general advice on these
errors and/or on maximising IIS potential for multiple connections.

Thanks,
--
Peter

Re: Connections being dropped by David

David
Mon Jun 23 20:16:06 CDT 2008

IIS6 has no problems scaling up to tens of thousands of concurrent
connections on default, untuned settings.

Performance will highly depend on the application running on IIS -- in
your case, the WebSphere plugin. That plugin is the first bottleneck I
would investigate since 10 concurrent users is far below IIS's normal
abilities. Perhaps the plugin is waiting on SQL -- turn on profiling
traces in SQL2005 for that segment.

http://blogs.msdn.com/david.wang/archive/2005/11/16/Thoughts-on-Connection-=
Abandoned-By-AppPool.aspx

My general advice on performance tuning IIS is to start by tuning your
application. IIS6 is pretty darn performant and scalable on default
settings, and only when you are certain your application is so darn
fast that IIS6 is bottlenecking it should you start looking at
maximizing IIS potential.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//





On Jun 23, 5:10=A0pm, Peter <Pe...@discussions.microsoft.com> wrote:
> Hi folks,
>
> We are doing some performance testing on a tiered app - IIS>WebSphere>SQL=
2005.
>
> We are running some scrip