- Decide between Early loading v/s Lazy loading or combination
- Size of Memory & CPU (not CPU intensive)
- Set LRU policy (will help Memory sizing)
- Latency
- What to cache and what to skip?
- Identify no. of Memcached instances and banks
- Select appropriate log levels
- Separate & manage Memcached logs
- Monitor Memcached servers (CPU, Memory,hits & misses of database and cache, etc)
- Ensure code coverage to leverage caching
- Test for thread contention
- Identify when to use get v/s multi-get
- Memcached allows us to scale out Application server instances. In case of multiple we need to take care of synchronization blocks (if any) used in our code.
Saturday, October 22, 2011
Memcached - Points to ponder
Few points to watch out in Memcached implementation and testing
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment