From: Philip Hallstrom Date: 2006-05-18T11:08:31+09:00 Subject: Re: bm + net/http sanity check > Ah ha, that makes more sense. It didn't occur to me that it would take > multiple roundtrips for a single GET. Gee, now that I think about it, that > doesn't include the image gets either... get() should just download the one page. It's not going to download the images contained within.... You might see if there is a head() (haven't looked, but i imagine there is). That will just query the server and the server will say "yeah, it's there", but won't return any data... -philip > > sd > > -----Original Message----- > From: Sam Roberts [mailto:sroberts@uniserve.com] > Sent: Wednesday, May 17, 2006 4:53 PM > To: ruby-talk@ruby-lang.org > Subject: Re: bm + net/http sanity check > > Quoting steve.debaun@seminis.com, on Thu, May 18, 2006 at 07:58:28AM +0900: >> Only reason I'm asking: ping delta is about 100 ms, but the Net::HTTP > delta >> is about 700 ms. This does not jive with what I'm expecting, at all. > > Why not? Sounds ok, setting up, using, and closing down a tcp line > should take at least 3 roundtrips, I think, so you'd need at least 300, > and if the data transfer takes a bit of time, bit of tcp stack overhead, > bit of software doing stuff... sounds like 700 ms. > > running tcpdump might tell you exactly whats going on, with pretty > accurate timestamps. > > Cheers, > Sam > > > This e-mail message may contain privileged and/or confidential information, > and is intended to be received only by persons entitled to receive such > information. If you have received this e-mail in error, please notify the > sender immediately. Please delete it and all attachments from any servers, > hard drives or any other media. Other use of this e-mail by you is strictly > prohibited. > All e-mails and attachments sent and received are subject to monitoring, > reading and archival by Seminis. The recipient of this e-mail is solely > responsible for checking for the presence of "Viruses" or other "Malware". > Seminis accepts no liability for any damage caused by any such code > transmitted by or accompanying this e-mail or any attachment. > >