H
Howard Hoffman
An ASP.NET Performance and scalability related question.
Given there are a set of 25 ASMX pages that stand independently (and that
don't call each other), all running on the same W2K3 WebServer.
Speaking purely from a scalability perspective, how would deploying the
ASMX WebServices as one single WebService application (read VS.NET 2003
WebService Project), dividing the pages into 5 separate WebService
applications (5 ASMXs per App), or even 25 different WebService
applications (1 ASMX page per App) affect the available number of ASP.NET
worker threads for each ASMX?
I seem to recall that ASP.NET has its own ICorRuntimeHost shim partly to
manage its thread pool differently than the standard .NET runtime.
TIA,
Howard Hoffman
Given there are a set of 25 ASMX pages that stand independently (and that
don't call each other), all running on the same W2K3 WebServer.
Speaking purely from a scalability perspective, how would deploying the
ASMX WebServices as one single WebService application (read VS.NET 2003
WebService Project), dividing the pages into 5 separate WebService
applications (5 ASMXs per App), or even 25 different WebService
applications (1 ASMX page per App) affect the available number of ASP.NET
worker threads for each ASMX?
I seem to recall that ASP.NET has its own ICorRuntimeHost shim partly to
manage its thread pool differently than the standard .NET runtime.
TIA,
Howard Hoffman