On: Writing a very fast cache service with millions of entries in Go

[golergka]

Straightforward, simple functionality, extremere perfomance requirements and avertion to allocations and GC?

That sounds like model use case for good old C. I love Go and currently am actively learning it, but why take a memory-safe, GC language and then build your own ad-hoc memory management on top of it to avoid it?

[_3u10 → golergka]

This is probably why the creators of memcached and redis chose C.