August 25, 2009 § Leave a Comment
First of all, I love Tokyo and already use Tokyo as secondary database for Pylons development and so far it has been a great success.
Since my box does not have a lot of memory, and a lot more disk space, it make sense to use Tokyo as caching solution instead of memcache.
Quick googling revealed that Jack Hsu has already implemented beaker’s Tokyo extension. His snippet works out of the box.
For my use case, I change the serializing strategy to using pickle instead of json. My reasoning is that pickle allows serializing complex object and I don’t have requirement for portability on cache data.
You can find the Tokyo extension here. I added Redis extension as well since it is very similar to Tokyo.
Edit (08/26/2009): Added extension for Dynomite
Edit (08/26/2009): Added extension for Ringo
[fixing bad layout]
April 21, 2009 § Leave a Comment
I’m currently benchmarking Moneta’s Tokyo vs Redis vs Memcache.
Results so far:
- Surprisingly, the Tokyo implementation is significantly faster. Even against memcache implementation. Why?
- Similar to LightCloud benchmark, the size of value does not affect speed of storing/getting.
March 9, 2009 § Leave a Comment
More and more KVDB projects are entering the scene, this time is Redis.
Why redis is cool? Writes to disk is perform periodically as opposed to immediate. Perfect for applications that are cache-heavy.
It boasted 100,000+ writes/sec. That’s pretty cool, the fastest benchmark I’ve seen so far. But don’t jump on it for mission critical application, yet. They just got started on implementing the replication. Just wait for a bit, from browsing the source, codes are checking in daily.