Performance improvements

[xaionaro]

Hello.

1. I'd suggest to consider using of fasthttp to reduce HTTP-library overheads.

https://github.com/valyala/fasthttp

A related issue: julienschmidt/httprouter#117

To make this project really useful you need to be faster than this:
http://antirez.com/blogdata/216/redisvsmemcached.png

2. Also, mutexes are slow. Especially on massively-concurrent cases (which a caching server is about). You may consider to use atomicmap instead (method GetByBytes to get a value) — it is oriented on a lot of reads (less writes and unsets [it's required to use LockUnset(), ATM :( ]).

https://github.com/xaionaro-go/atomicmap

http-cache/cache.go

Line 36 in 91198cf

c.Mutex.Lock()

Or, may be, it would be better to implement own mutexless thread-safe map.

3. You're coping data (and doing a memory allocation) here:

http-cache/cache.go

Line 24 in 91198cf

if value, ok := c.Map[key]; ok {

I'd suggest to use pointers, instead.

[Darwinnn]

Hello!
Well, first of all, I'd like to thank you for the feedback! I'll consider what you suggested here and come right to it.

[Darwinnn]

1. Also, mutexes are slow. Especially on massively-concurrent cases (which is about a caching server of)

I've done some tests and it looks like atomic sync.Map is slower (about to 5k rps) than plain map with mutexes. At least on my 4cores i5 cpu. I'll be looking to test your lib and compare the results

[Darwinnn]

1. I'd suggest to consider using of fasthttp to reduce HTTP-library overheads.

Wow, that actually doubled the RPS value.