s-bose7 / memcache Goto Github PK

Key metrics to record:

• Hit/Miss Ratios
• Request Counts
• Eviction Counts
• Expiration Counts
• Latency
• Memory usage

Callers should have the ability to enable or disable serialization and compression when creating an instance of cache object. One can use a configuration object or parameters passed during the construction of the cache.

A lazy TTL doesn't require any background job.

During a get call, the main thread will check whether the requested Key is outdated, if it is, key will be removed immediately and nothing gets return.

Useful for storing all relevant metadata about the keys in one place.

The raw size is an approximation of the storage requirements in cache_banchmark.cc. Use a method to dynamically evaluate the required storage in megabytes.

When the cache is created with a value type string: MemCache<key_type, string>, serialization and deserialization wouldn't work properly and results in memory corruption.

Probable solutions would be to handle the type "string" separately by overloading serialization and deserialization methods to handle string data type; or not serializing the data in the first place, can be done by checking the type earlier before serialization.

The later process works because we need string in order to compress the data, but as we have already string as the value data type, the constraint doesn't apply anymore.