Web service: resource managment
-
I have a webservice that takes a byte[] parameter and writes it out to the filesystem. The byte[] is about 120k in length (on average). The webservice can be hit about 20x per minute (so that puts it at about 2.5mb/min). The system administrator is saying this service is causing bottlenecks and other web services/web apps are also failing as a result. He suggest that i change the code to speed up the webservice because it's using up too much resources. The code is pretty straight forward. I don't understand how this webservice is breaking the other applications/services. I was under the impression that the resource management (thread managment, memory manamgement) is all done under IIS not in the code behind. If i'm not correct what could i possibly do (either in the web.config or code behind) to prevent this from happening. Someone suggested that i monitor the threads in the webservice but that really doesn't make sense to me. I'm totally confused on this subject. Thanks,
Don't be overcome by evil, but overcome evil with good
-
I have a webservice that takes a byte[] parameter and writes it out to the filesystem. The byte[] is about 120k in length (on average). The webservice can be hit about 20x per minute (so that puts it at about 2.5mb/min). The system administrator is saying this service is causing bottlenecks and other web services/web apps are also failing as a result. He suggest that i change the code to speed up the webservice because it's using up too much resources. The code is pretty straight forward. I don't understand how this webservice is breaking the other applications/services. I was under the impression that the resource management (thread managment, memory manamgement) is all done under IIS not in the code behind. If i'm not correct what could i possibly do (either in the web.config or code behind) to prevent this from happening. Someone suggested that i monitor the threads in the webservice but that really doesn't make sense to me. I'm totally confused on this subject. Thanks,
Don't be overcome by evil, but overcome evil with good
well it happens sometimes to send lots of data to the webservice and also return a lot. Try to check if you are not sending or receiving any unnecessary data. Also for your webservice, each time it is called the web server spawns a new thread and runs it. Try not to open any new thread from the web service if not absolutely necessary. And in IIS host the webservice in a new application pool.
Abhishek Sur My Latest Articles Working with Excel using MDAC
Basics on LINQ and Lambda Expressions
Create .NET Templates -
well it happens sometimes to send lots of data to the webservice and also return a lot. Try to check if you are not sending or receiving any unnecessary data. Also for your webservice, each time it is called the web server spawns a new thread and runs it. Try not to open any new thread from the web service if not absolutely necessary. And in IIS host the webservice in a new application pool.
Abhishek Sur My Latest Articles Working with Excel using MDAC
Basics on LINQ and Lambda Expressions
Create .NET Templates