good chemistry is complicated, and a little bit messy -LW |
|
PerlMonks |
Re^13: Async DNS with LWPby BrowserUk (Patriarch) |
on Oct 08, 2010 at 11:10 UTC ( [id://864182]=note: print w/replies, xml ) | Need Help?? |
I'm sorry, but worrying about async DNS at this point is ... well, pointless. Let's do some math. With your current setup, 90e6 sites with say an average of 100k per home page(*). To download that lot in your 100 hour allocation, you'd need to be fetching constantly at a rate of 25Mbytes/s. That would would (conservatively) require a 250Mbps connection. To do it in your target 3 hours you'd need an 8 Gbps connection. Now, I'm not sure what data rates you can achieve with GSM (GPRS,EGPRS) in the US, but I'm pretty sure they'll be measured in 10s of Kbps. Not Mbps much less Gbps. Even once you moved to your hoster, if you could sustain their 100Mbps burst rate indefinitely, 90e6 * 100k would take ~250 hours to download. And they'd cut you off long before that. Worrying about shaving a few milliseconds here and there using asynchronous DNS is just a drop in the ocean. (*)They seem to range from the minimalist google at 8k, up to the commercial bloat of sky.com at 250k; but 100k is a good average of the few I looked at. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
In Section
Seekers of Perl Wisdom
|
|