Announcements, New Features, and How Tos
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.
We made a slight change to the analytics dashboard to show 30 days of usage data. Previously we were only showing 7 days. Take a look at your dashboard and tell us what you think.
Despite being the go-to scaling solution for most production websites, Memcache often isn’t used to its full potential. Most developers only know about the
delete operations. However, Memcache has a broader set of operations that help developers build more advanced apps with less code and even further improved performance.
We’re excited to announce that MemCachier is now available in EC2, AppFog, dotCloud, and CloudBees. Now developers can speed up page loads and improve their app’s scalability with MemCachier’s memcache solution.
Today we’re announcing the general availability of our analytics dashboard – a simple tool to give you more insight into how you’re using memcache.
This dashboard is the start of what will eventually become the most advanced usage analysis tool available. The current feature list includes:
- Current usage: bytes and number of objects
- Usage history, in bytes
- Cache flush button
Moving forward we plan to provide much more in-depth usage statistics. We’re already working on the next version – let us know if you have feature requests you’d like us to consider.
2pm rolls around and you’re already tired of sitting all day. So you slouch over your computer for the rest of the day. By the evening you’re exhausted, your back and wrists are sore, and you’re dreading doing it again tomorrow. Sound familiar?
We got tired of sitting so we built $22 standing desks, constructed from IKEA parts and wood screws.
Update (August 27th, 2018): An article explaining how to find the ideal cache size can be found here.
A larger memcache can sometimes enable better performance and scalability. But not always. Some of our customers have benefited from a larger cache, while others haven’t. In this post we’ll explain how to determine if you need a larger cache and how a larger cache improves performance. This post assumes you already have a basic knowledge of memcache – refer to our Memcache user guide if you don’t.
Last week we answered the question, “Why should I use memcache?” Now we’ll get a little deeper into the usage of memcache by showing some example code, along with detailed explanations. This post will give you an idea about what it takes to write memcache code to help your app scale. We’ll use pseudocode to demonstrate.