3 ms·
Interesting to see Tokyo with so few votes. On benchmarking it had the smallest memory footprint when loading ~17GB of packed binary data. Been awhile but I rem
by ghotli 15y ago
Interesting to see Tokyo with so few votes. On benchmarking it had the smallest memory footprint when loading ~17GB of packed binary data. Been awhile but I remember testing redis, postgres, mongo, and bdb. This let us keep all the low latency read-only data we needed available in memory and provision the smallest possible machine to do it.
- mycatverbs 15y agoI bet a lot of the proportion is down to most people writing in with what they use in their day jobs. Also, while I love Tokyo's speed, it is just a better bdb - which is an impressive feat, but I can see why a lot of people would use something slower but more featureful.
- davidhollander 15y agoTokyo is my standard database for personal projects and goes great with Lua. Both are lightweight and fast, Cabinet has an excellent binding, and Tyrant has embedding.