Server migration finished (with new server latency data)
If you're seeing this, then you are looking at the new server! It will take 24h for the DNS changes to propagate to these new servers, then the old server infrastructure will be shut down and securely wiped.
My apologies for the ten minutes of downtime earlier today - it turns out that the documentation for making a ZEO based Plone site read-only is severely out of date, so I have submitted updated docs to the Plone FAQ.
Enjoy the considerably faster new server cluster - it's about 200% as fast for cold page loads, 600% faster for warm page loads (see page load times archive here) and can handle several dozen times more maximum simultaneous users! We would also like to announce that due to reliability problems we have disabled the Los Angeles cluster which will shortly be decommissioned - all global traffic now goes to Amsterdam. In case you are wondering about the effects on ned Productions Ltd hosted websites:
The first graph shows the current and former european latency profiles whereas the second graph shows the former geo-targeted profile (note that the two graphs can't be directly compared as their test locations and times are very different, however the blue line is for the same top quality London Docklands based server in both despite the up to 100ms difference ). As you can see, the new Amsterdam cluster isn't as well connected outside Europe as it could be with its 50-100ms extra latency, but sometime in early 2011 we hope to open a data content caching node in Phoenix, Arizona for much improved global data read latency.