Moved IPVM To A New Server, Now 35% Faster

We moved the IPVM application / site to a new server [Update: the site is now 35% faster]

Here's a few technical details for those of you interested in server selection / specs (see previous discussion on picking servers).

Previous - Rackspace

We have been...

* ****="****://***.*********.***/" ******="******">*********, ****** **** ****** ** ********** **** *********, a ***** ******* **********, *** ** ** **** (** **) when ** *******. **** ****** *** *** ***, ** ** hard ***** *** * '*****'. ** **** ~$*** *** *****.

********* *** **** **** *** **, *** *****, *** ** major ******. *** **** ********** ****** ** **** *** ****** has *********** * ***** ** '****' **** ******* ******* *** experiments (********** ** ** ** *** ***** ****).

New - ******* *****

** **** ***** ********* *****, ***** ** * *** ** *** ****** ******** (*** '*** ******** **** ** ******* *****'). ***** **** ********* ***** ** ***** *** ******* ******* of **** ******. *** ***** *** ********* ************** ** ****, for *** ************* ** *** ********* ******, **** ******* *** *** (** more) *** * ***** (******* ** *).

Why *** * ********* ******?

** ********* ***** ** * ********* ****** *** ******** ** (both ******** *** *** ****** *** *******). *** **** ***** is **** ** * ************ ******** ******* ********, ** ***** be *********** *** ******* ** *** ***** ** * *** machine - ** ***** **** ***** ** ********* *** *********** both *** ** *** *** *** ******* *** ***** **** access ****** **** **** (****** *****, ** *** **** ** a ***, ********* **** ** ********). *** **** ********* ****** would ** ******* *** / *** *** **** ******* *****'* 8GB / * **** / ** ** *** *****, ****'* far **** **** ****** *** **** ** **** **** **** we ****** ******* *****.

******, *** ** **** ** *** **** ********* ** ********.


The new server is live. It feels to me significantly faster and some single page tests confirm that. However, I'll know more when after a few days of traffic.

Also, one minor note - the server is now physically in NY instead of TX which might make a slight difference / benefit to East Coast visitors. That said, I am still in Honolulu and it still feels faster to me.

so this relates to "cloud video" and other things "in the cloud" where suddly the ISP's routing vaguaries can impact your business. Traceroute to the site looks fine, although the packets wander around inside Level 3's network in NYC a bit long as they finally figure out they need to go to Newark ("tracert www.ipvm.com".) "ping -n 100 www.ipvm.com" looks solid from cloud hosts (in Fremont, CA and Chicago, IL). Kinda wild variations in time from the coffee shop I'm sitting in in Berkeley CA but I doubt that's you. DNS servers are sanely diverse. And I never noticed until I saw the post, it's not like I had an issue before you incentivized me to go all wine-snob about your hosting provider choice.

Ping tests from HNL to the ipvm server in NY/NJ range from 135 - 150ms. Traceroute shows a few hops in DC and NYC (but total time is like 10 - 20ms for that).

The big issues in web applications are typically client side/page rendering (javascript, images, etc.) or server side (database lookups, the application itself, etc.), not network. We've cut at least a few hundred milliseconds off the server side portion which is a huge gain overall.

The site is now 35% faster overall, which is a huge jump. Previously, average load time was a pedestrian 4.6s, now it is a fairly strong 3.0s. I confirmed this even after the spike in traffic from our newsletter today. I am happy about this.

That's a reduction of 5~ days loading each month for all members (250,000+ page views x 1.6s per page).

Ahh, yes, but what is the "real world" practical expected savings in load time? Remember, one 10MP camera does not replace 20(D1) cameras, or whatever it is.

=)