Deltax76
Deltax76

Reputation: 14263

How to break the limitation of ASP.NET webservice?

I'm writing a ASP.NET webservice (.ASMX), and to test this webservice, I'm using a client application which creates 100 threads, 3 requests/each thread. When I run 10 iterations, the client takes about 60-70 seconds, which means about 3000 requests/minutes, and I can't manage to take over that number, even when I run the client and the webservice on same machine. I checked all the statuses of machine: RAM, hard-disk, CPU,... all the statuses are OK (very low-load, CPU below 6%, RAM about 80% free,...), and the bottle-neck is the webservice itself.

I tried WCF, but it performs worse than the ASMX in my benchmark, and because of my deadline, I can't spend too much time to study deeper WCF.

So how can I optimize my webservice? How can I break the limitation of ASP.NET webservice? Is it possible to manage to get a webservice to perform up to 5000 request/second?

Thank you very much.

Upvotes: 2

Views: 433

Answers (1)

Mr Shoubs
Mr Shoubs

Reputation: 15399

In addition to trying asynchronous web requests - though there is an easier way of doing this - I think it is in the properties of the web service reference that allows the async methods (and related completed event) to be generated in the web service proxy,.

Have a look at SOAPUI and LOADUI, they are tools that could help you.

Upvotes: 3

Related Questions