Webservice performance poll - will this work?
Our application needs instant notification, so obviously I have to use some WCF duplex or socket. The problem is that the application is a partial trust of the XBAP and so I don't allow anything other than BasicHttpBinding. So I need to poll for changes.
No question: my PM says the refresh interval should be 2 seconds and run on an intranet with 500 users on one web server.
Do any of you have any experience how a survey will affect a web server.
The service is very simple, it takes a directive as arg and returns a list of commands. All data access is cached, so my guess is that the load on the server is minimal for one call, but for 500 ...
Except for polling, the web server has little work to do.
So, based on this little information (assuming a standard HW server, whatever it is), is it possible to qualify guesses?
- Is it possible to implement it or not, will it work?
Yes, I know it is difficult, but I would be very happy if some of you could share some thoughts on this.
Hello
Larsi
The poll is .. bad, but if you have no other choice then it is perfect :)
Remember that you will no doubt have your rights, so you will have 500 permanently connected users. Memory usage is likely to be more significant than CPU usage. I can't imagine that network access (even in a rather bloated web service) would use up a lot of network bandwidth, but your network latency could be an issue - especially since we've all seen web applications pause for a while.
In the end, you will probably be fine, but you will have to check it out for yourself. There are tons of stress testers for web services, you can use Microsoft WAS tool for one, here are a few links to others.
source to share
I don't think this will be a particular problem. I would imagine the response times for each request will be pretty low unless you drop a lot of data, so 500 connections propagating over 2 seconds shouldn't bump hard about it.
You can use a stress testing tool to make sure your web server can handle the load, but before doing this project.
source to share
250 qps is probably doable with fairly modest hardware and network bandwidth, provided you minimize the data sent back and forth. I am assuming you are caching these GUID lists on the client so you can just send a small "no updates" response in the normal case.
Should be fairly easy to measure with a simple prototype, but to be more confident.
source to share