NSURLRequest/connection timing
NSURLRequest/connection timing
- Subject: NSURLRequest/connection timing
- From: lcerveau <email@hidden>
- Date: Wed, 14 Sep 2011 20:19:56 +0000 (GMT)
Hi
I have a question regarding time a NSURLRequest/NSURLConnection is taking and the internal of it. I already asked to cocoa-dev but was advise to ask on this one.
I do the following
- When creating/launching the request I take a timestamp,
- in the delegate method
- (void)connection:(NSURLConnection *)connection didReceiveResponse:(NSURLResponse *)response
I take another one. I have results like 0.6 seconds.
I have to launch multiple request at nearly the same time to the server (like 20)
- At the same time I use a software like HTTPScoop to look on how it is timing all this. Time are always différent like 0.05 seconds.
So nearly always a factor of like 10.
Who to believe on the time it takes?
As all the requests are against the same server and this one is supporting the use of setHTTPShouldUsePipelining. But it seems not to provide any speed gain and looking at the result I have the feeling requests are send before the previous one returns, that the server answers correctly but that the low level implementation of NSURLRequest/NSURLConnection is delivering them one after the other loosing the benefit of pipelining. Or do I miss a part here?
Thanks
laurent
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden