Calling web service from web page; concurrency problems?
From: tale (tale_at_juno.com)
Date: 03/30/04
- Next message: starbuck: "Re: using frames in asp"
- Previous message: Peter O'Reilly: "Response.Redirect"
- Next in thread: bruce barker: "Re: Calling web service from web page; concurrency problems?"
- Reply: bruce barker: "Re: Calling web service from web page; concurrency problems?"
- Messages sorted by: [ date ] [ thread ]
Date: 30 Mar 2004 08:18:14 -0800
Hello all,
I really need an answer to this post, so I'm trying to repost it. My
question is below. I've included all of the original posts below.
Here is my questions to the last response.
> actually this limit applys to asp.net. the default behavior for asp.net page
> making webservice calls is still two connections per server. you
> canoverride this limit at runtime.
>
Ok, so this does apply to asp.net.
> the reason for the limit is net etiquette. one client is not supposed to
> overuse a remote resource. in this case your web server is the client, but
> the rule is same, you should not overload a remote server unless you know
> its ok, so the override should be on a server by server basis.
So does this 2 connection limit apply to each page, the web site
(assuming you are running multiple sites on one server) or the server
itself?
If it applies to the server, then I have another question. In my
first post, I stated that I thought passport used web services. How
can this limit apply to the server and these web sites that use
passport still handle the amount of concurrent page view thst they
normally handle?
-- Tale
Here are the original post and responses:
actually this limit applys to asp.net. the default behavior for
asp.net page
making webservice calls is still two connections per server. you
canoverride this limit at runtime.
the reason for the limit is net etiquette. one client is not supposed
to
overuse a remote resource. in this case your web server is the client,
but
the rule is same, you should not overload a remote server unless you
know
its ok, so the override should be on a server by server basis.
-- bruce (sqlwork.com)
"Martin Dechev" <detcheff_@hotmail.com> wrote in message
news:OiaH8hoEEHA.1272@TK2MSFTNGP12.phx.gbl...
> Hi, tale,
>
> What you are referring is the limit for the connections through WinInet API,
> which does not apply to the IIS, but to the client applications that need to
> connect to the internet.
>
> The actual number of maximum concurrent incoming connections to a website is
> controlled in the machine.config file in the <processModel> and
> <httpRuntime> sections, namely maxWorkerThreads and maxIoThreads in the
> processModel element and minFreeThread in the httpRuntime element. See:
>
>
http://msdn.microsoft.com/library/en-us/cpgenref/html/gngrfProcessmodelSecti
on.asp
>
http://msdn.microsoft.com/library/en-us/cpgenref/html/gngrfHttpRuntimeSectio
n.asp
>
> Basically, if you don't write crazy pages that start a bunch of threads the
> maximum number of requests handled simultaneously is ((maxWorkerThreads per
> CPU) - minFreeThread). With the default values in the machine.config for a
> single-CPU machine this results in maximum of 12 concurrent requests handled
> simultaneously.
>
> Hope this helps
> Martin
> "tale" <tale@juno.com> wrote in message
> news:329cbf39.0403250734.3f5c6d3b@posting.google.com...
> > Hello all,
> >
> > I'm writing an ASP.NET web page that will call a web service. Another
> > developer here stated that he believed that due to the System.Net
> > connection limit being set to 2 that only two connections can be made
> > from the web page to the web service. We are expecting many
> > concurrent page loads.
> >
> > I was wondering if this is really a problem for web pages. Does the
> > two connection limit apply to the whole web site or just the web page?
> > If it applies to the web site, then how does all of the ASP.NET web
> > sites that use passport get around this problem? I believe that
> > passport authentication uses a web service. If I'm correct in my
> > assumption, then these busy sites that use passport for authentication
> > would definitely be authenticating more than 2 people at a time. Do
> > the other web pages have to wait on those two connections?
> >
> >
> > Here are two links that I've found that talk about the limit. If you
> > can prove or disprove my assumption, please provide me some links to
> > documentation so I convince this other developer.
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;183110
> >
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
l/cpconbestpracticesfornetclasses.asp
> >
> >
> > Thanks in advance,
> > -- tale
>
>
- Next message: starbuck: "Re: using frames in asp"
- Previous message: Peter O'Reilly: "Response.Redirect"
- Next in thread: bruce barker: "Re: Calling web service from web page; concurrency problems?"
- Reply: bruce barker: "Re: Calling web service from web page; concurrency problems?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
