4 ms·
Meh, it's a decent and properly commented implementation, but the interesting stuff is done by Redis, not in Go. I wrote a similar service (JS+Go) 2 years or s
by lazyjones 12y ago
Meh, it's a decent and properly commented implementation, but the interesting stuff is done by Redis, not in Go.
I wrote a similar service (JS+Go) 2 years or so ago using only the Go standard library (specifically the excellent index/suffixarray and gobs for persistence). It typically got ~3ms response timings (locally) with > 1 million records indexed.
- peterbe 12y agoI wrote a cache layer in Go (with limits so it doesn't bloat too much) and I could get 22K req/s instead of the usual 4K. However, the hit ratio is too low to work. It only protects me from the stampeding herd problem at best.
- chralieboy 12y agoWhy does it matter where the interesting stuff is implemented? Do you have a link to your implementation or comments on how this one could be improved?
- jamra 12y agoI wrote something comparable. It's at github.com/jamra/gocleo. It is based on a Java implementation. Would you care to link to what you wrote?