T
TomR
We are having problems with synchronus web request calls
blocking our ASP.NET performance. Here is the setup:
We have an aspx script on Site B with a synchronous
HttpWebRequest call to access Site A (simulating accessing
a bank credit card payment gateway). The page on Site A
currently does nothing more than wait 15 seconds before
serving a page, again simulating the potential lengthy
response from such a site.
When we open four browsers on the aspx page on Site B
"simultaneously" (which in turn causes the lengthy wait
accessing Site A), only two pages get served at a time.
The first two take 15 seconds, the second two take 30
seconds. We thought maybe this was due to make the
eequests from the same IP address, but we tried the same
thing on four machines with four different IP addresses as
clients, and got the same results (first two transactions
take 15 seconds, second two take 30 seconds).
We tried several different things including asynchronous
web requests and it seemed to make no difference. Only two
requests ever got processed at one time.
We are anticipating having to process perhaps 50 of these
transactions simultaneously, and if only two are being
processed at any given moment response time would be
horrible. I'm sure we aren't the only ones trying to do
such a thing. What might we doing wrong to cause this
behavior?
Thanks,
TomR.
11648409
blocking our ASP.NET performance. Here is the setup:
We have an aspx script on Site B with a synchronous
HttpWebRequest call to access Site A (simulating accessing
a bank credit card payment gateway). The page on Site A
currently does nothing more than wait 15 seconds before
serving a page, again simulating the potential lengthy
response from such a site.
When we open four browsers on the aspx page on Site B
"simultaneously" (which in turn causes the lengthy wait
accessing Site A), only two pages get served at a time.
The first two take 15 seconds, the second two take 30
seconds. We thought maybe this was due to make the
eequests from the same IP address, but we tried the same
thing on four machines with four different IP addresses as
clients, and got the same results (first two transactions
take 15 seconds, second two take 30 seconds).
We tried several different things including asynchronous
web requests and it seemed to make no difference. Only two
requests ever got processed at one time.
We are anticipating having to process perhaps 50 of these
transactions simultaneously, and if only two are being
processed at any given moment response time would be
horrible. I'm sure we aren't the only ones trying to do
such a thing. What might we doing wrong to cause this
behavior?
Thanks,
TomR.
11648409