jtai

5 ms·

1. 1.▲
   by jtai 13y ago

   Comparison to shared memory or mmap'd files -- by using files we let the filesystem manage the cache, so we don't have to be concerned with the data growing and causing memory pressure. We also don't have to worry about how t
2. 2.▲
   by jtai 13y ago

   Our community of translators update translations all the time. Updates are immediately reflected so that our translators have instant feedback, and we'd like our users to see the updated translations sooner than every time we deploy to
3. 3.▲
   by jtai 13y ago

   We ended up using sparkey as the first backend for hammerspace, but hammerspace was written to support multiple backends. We benchmarked both cdb and sparkey, and their performance was very similar for our use case. At under 100mb of data,
4. 4.▲
   by jtai 13y ago

   Good points! We did initially try dedicating ruby processes to particular locales -- when we saw a big improvement we knew we were on the right track. Doing so permanently would be more difficult. To "follow the sun" we would need
5. 5.▲
   by jtai 13y ago

   We did benchmark local memcache, but accessing the strings over the network (even locally) was much much slower than sparkey. Redis would likely have been similar to memcache. The savings came not just from avoiding redundant GC over the sa