"Eran" <dveyaharon@gmail.com> wrote in message
news:1157441035.291330.136160@b28g2000cwb.googlegroups.com...
> Hi,
>
>
> I have a Soap web service (.NET 2.0) on machine Y.
> I have a tester program on machine X invoking calls on Y. X is
> multithreaded, and I test the performance on Y calling 1,3,5,10,30
> users.
>
> I keep getting a strange phenomenon, maybe someone can put some light
> on: *most* threads are invoked simultaniously, but some are searialized
> and start only after other threads ended.
> When I run 30, 27-30 start together, when I run 10 - 7-10 run together
> etc.
>
> It doesn't seem like a problem in the client (I've increased any
> maxconnection and maxthreads parameters on the machine.config and
> app.config. I couldn't find anything on the server as well (it doesn't
> reach high resources in anything).
> Even when I run the client from the same machine, the phenomenon
> happens (though more rarely).
>
> I use perfmon on the server, and the counter 'ASP.NET' -> 'Requests
> Current' shows the amount of parallel requests running, and shows the
> problem. When I run 10 and it shows 8, 2 requests will start much later
> on the server. However, I can't see them queued anywhere. (The requests
> Queued' is 0).
>
> The most bizare thing is that it happens sometimes even with 2 requests
> (though the capacity of the server is much much much higher than 1).
>
> Any ideas?
>