Announcements, New Features, and How Tos
We took down our blog for a long time after we moved from our website being a modified WordPress installation, to a custom built Ruby-on-Rails job. Sadly, we never got around to putting it back up.
On the 12th of March between 2am and 11am PST MemCachier suffered a series of outages and performance problems for many of our production customers. This post briefly summarizes the cause of the problem and the actions that have been taken since to address it.
At 3:36pm PST we had a large number of failures across the board with our production cluster. We quickly found that a single machine (MC4) was responsible for this. We run a distributed cluster that scales extremely well but also ties many machines together such that a single failing machine can cause unresponsiveness though out a lot of the cluster. We are actively working on strategies to manage this coupling better.
Check out our WordPress tutorials:
MemCachier can now power your WordPress object cache thanks to a plugin Per Søderlind created. The WordPress object cache is used to cache computationally expensive operations such as complex database queries. By using Per’s MemCachier WordPress plugin, you can speed up page load times for your readers and get all the added benefits of using MemCachier to power your cache – easy setup, high availability, and an analytics dashboard.
We are excited to announce that MemCachier will be taking part in a webinar put on by our friends at Joyent. The webinar will be a panel based discussion on the topic of Do-It-Yourself Vs. as-a-Service model and will take place next Wednesday the 12th of December at 10am. We hope the discussion of the trade-offs and benefits will be rewarding to all participants. Questions will be from audience members, so if you’ve ever wanted to chat with us (David will be on deck), then this is your chance!
Some of our customers in Amazon’s us-east-1 region (Virginia) noticed degraded performance and partial outages starting Friday, 11/16 through Sunday, 11/18, and again on Wednesday, 11/21. We want to take this opportunity to explain what happened.