Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Performance / July 2004

Tip: Looking for answers? Try searching our database.

Thread pool and HTTPRequest

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Brendan - 05 Jul 2004 14:25 GMT
Hi,

I'm trying to use the .Net httpWebRequest objects to make asynch calls.  I'm creating a crawler and I'm hoping to increase performance.  Initially I was running into thread pooling issues but was able to find a way to increase the default 25 threads.  This has partially solved my problem.

Now, my problem is that I get better performance going through a proxy server than a direct connection.  The behaviour I'm seeing is that the proxy allows the requests to be queued much quicker than if I'm running locally.  I'd like to be able to not use the proxy server but haven't been able to get performance near that of going through a proxy.  Any help in suggesting a way of increasing request/response time outside of a proxy would be greatly appreciated! :)

Thanks,
Brendan
Feroze [msft] - 16 Jul 2004 20:09 GMT
What do you mean by "performance" ? Is it that the pages are being
downloaded faster than if you hit the server directly ?

IS the server you are accessing on the same network as the client ?

Are you downloading dynamic contnet (as opposed to static content) ?

It might be that the proxy server is serving the pages from it's cache, that
is why it is faster.

feroze
=====================
this posting is provided as is. It offers no warranties and confers no
rights.
=====================

> Hi,
>
> I'm trying to use the .Net httpWebRequest objects to make asynch calls.  I'm creating a crawler and I'm hoping to increase performance.  Initially I
was running into thread pooling issues but was able to find a way to
increase the default 25 threads.  This has partially solved my problem.

> Now, my problem is that I get better performance going through a proxy server than a direct connection.  The behaviour I'm seeing is that the proxy
allows the requests to be queued much quicker than if I'm running locally.
I'd like to be able to not use the proxy server but haven't been able to get
performance near that of going through a proxy.  Any help in suggesting a
way of increasing request/response time outside of a proxy would be greatly
appreciated! :)

> Thanks,
> Brendan
Justin Rogers - 16 Jul 2004 20:31 GMT
To add, have you looked at ServicePoint's and the possibility that you are
making a maximum of two connections to each server at a time without
raising the limit? The proxy probably shuns the 2 connection limit while
the ServicePoint classes used by the HttpWebRequest does not. Try raising
your limit a bit and see if that helps. I ran into a similar problem making a
multi-part download application.

Signature

Justin Rogers
DigiTec Web Consultants, LLC.
Blog: http://weblogs.asp.net/justin_rogers

> What do you mean by "performance" ? Is it that the pages are being
> downloaded faster than if you hit the server directly ?
[quoted text clipped - 29 lines]
> > Thanks,
> > Brendan

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.