Re: Asynchronous calls to a web service - 100,000 a minute
- From: "Jeremy" <nospam@xxxxxxxxxx>
- Date: Fri, 28 Sep 2007 09:53:04 -0700
How often does the data in the table change? Even if the clients poll once
a minute would they be getting new results each time?
I ask because it may be worth your while to make a "proxy web service".
Once that your clients can call, which would in turn call the real web
service but cache the data for 1 or so minutes. Only when the cache expires
would the proxy web service actually call the real web service and update
the cache. That way the real web service only gets called 1 time every
minute and there's only a database hit 1 time every minute. Your proxy web
service would get hit a lot but 99% of the time it would be dishing out
cached data, making it able to serve more hits. The bottle neck now becomes
your proxy web service, but if you found the load on that web service was
too high, you could put it on more than one server, splitting the load up.
<kebalex@xxxxxxxxx> wrote in message
news:1190969455.012459.52310@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
I've got a requirement to poll a web service for data but it needs to
be done very frequently. The web service call is straight forward,
it
just returns a simple table of data with no more than 50 rows. It's
a
third party web service so i have no control over it. The problem is
each call is on a per user basis and the client said if its succesful
it there could be 100,000 users. The frequency of each call could be
once a minute so that could be 100,000 calls a minute.
I'm designing the client app to make the requests and i'm thinking
each
request should be asynchronous but i'm not sure this is enough. I've
got
no experience of multi-threaded development so i'm not sure if this
would help (making the requests over many threads).
Also I'm concerned about bottlenecks. If the app I built was capable
of making 100000 requests a minute (possibly at the same time if its
multi-threaded) then would the network handle this load and also
could
the web service handle this many requests at once (i know the W3C
recommends only 2 client connections at once so that could be an
issue).
Anyway, any help or thoughts would be much apprecieated.
Thanks,
Alex
.
- References:
- Asynchronous calls to a web service - 100,000 a minute
- From: kebalex
- Asynchronous calls to a web service - 100,000 a minute
- Prev by Date: Re: Best way to design multithreading application
- Next by Date: Re: Best way to design multithreading application
- Previous by thread: Re: Asynchronous calls to a web service - 100,000 a minute
- Next by thread: Re: Asynchronous calls to a web service - 100,000 a minute
- Index(es):
Relevant Pages
|