31–40 of 240 posts
While the WiFi in most hotels is horrendous, wired internet is pretty awesome most of the time. A network cable is always in my suitcase and my laptop can run as an access point for my other devices. A separate access point could also come in handy (you have very small ones nowadays). During JSDay.it people had a lot of time even connecting to the WiFi while I was running at 80 mbps.
Was considering doing this for all wifi networks. I have an API built in Rails for it if anyone wants it (100k+ public wifi hotspots, such as coffee shops, restaurants, etc), shoot me an email: josh@josh.mn
I'd like latency as well as speed. A lot of hotels I have been to have really high ping times.
Yes, latency is very important. We found that there is a strong negative correlation between bandwidth and latency (faster connections tend to have lower response times). That's why we decided to focus on speed first. We are planning to add ping testing as well.
While the WiFi in most hotels is horrendous, wired internet is pretty awesome most of the time. A network cable is always in my suitcase and my laptop can run as an access point for my other devices. A separate access point could also come in handy (you have very small ones nowadays). During JSDay.it people had a lot of time even connecting to the WiFi while I was running at 80 mbps.
The potential downfall of general measurements like this is large conferences like WWDC, where if there's a geek in every room, the whole-hotel performance is going to suffer unless they've provisioned massive peak bandwidth. (Thinking of the Marriott near Moscone.)