3 ms·

Hi jacques, Regarding the request time, if you stay in the datacenter, the response time is very very low. (to the ms). Regarding the production, right now it'

• jacquesm 16y ago
  You should do a benchmark of some simple page that uses no caching, memcached locally and memcached remote but in the same datacenter, that would be interesting information. We don't use Linode, but we do use memcached to store 'partials', and for now I'm skeptical about running that memcached on the other side of a wire, latency tends to fluctuate quite a bit in a busy DC, so you may have to run your test over an extended period of time to get good data. It helps if your machine is equipped with two ethernet interfaces, one for 'local' traffic and one that is facing the outside world.
  • mtigas 16y ago
    I'm not sure how Linode does it, but I've worked on dedicated machines that have separate, internal routes. (Slicehost VPSes have this option available -- unmetered -- too.) When compared to heavy processing on large database queries, memcached -- even with a few extra ms of latency -- can still be a major performance win. Although this largely depends on the applications you're making. I've been working with GIS applications lately, where a large distributed cache (most memcached clients automatically support sharding) is about the best you can do without a large hardware budget.
    • wwortiz 16y ago
      Linode allows internal routes as well, and it is unmetered (it just has to be in the same datacenter, though that should be a given).