URL Access performance tuning
URL Access performance tuning
- Subject: URL Access performance tuning
- From: "Pietrzak, Bryan" <email@hidden>
- Date: Tue, 14 May 2002 15:18:16 -0600
(the cross post seemed appropriate in this case...)
I'm using the URLAccess APIs in Carbon to download 1-n files from a remote
HTTP server.
A few questions:
1) What is the best frequency to use for URLIdle()? The URLAccessSample code
is calling it from a timer every millisecond. That seems pretty frequent,
but is that the ideal value?
2) How many concurrent downloads (via URLOpen) can I make? Should I wait
until each file is downloaded before grabbing the next one, or should I have
2, 4, 8, ? concurrent downloads going to make better use of resources? All
files will be downloaded from the same server if that makes a difference.
3) How performant (is that really a word?) is URLAccess in Carbon on OS X?
Is it built on top of Open Transport, or does it use a lower level
implementation built on top of CF, or does it use BSD sockets? Basically, I
guess I'm asking, how "bad" is it for me to use URL Access to download a
bunch of files? Am I burning an extraordinary number of CPU cycles and
wasting network resources?
Bryan
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.