Quang Tùng

> Any update on this? I think version >= 1.3.4 should already fixed this

May be you should try my implementation of memcache client: https://github.com/QuangTung97/go-memcache It uses TCP Pipelining & Batching + Connection Round Robin to connect to the memcached server. It support mostly...

Or it should be fixed like in this comment: https://github.com/jmoiron/sqlx/pull/734/files/4b6b69ec278c1fbfafba4336f8c84065b0911029 Could make the solution works with more cases.

> I have to agree with @tessus . Maxmemory simply does not do what is described. This is totally different than memcached, hyperdex or aws rds. > > We have...

@garry-t What is the distribution of key sizes of your stress test. I think the OOM will be more likely when there are a wide range of key sizes

Any update on this? I also got this error logs when I do the stress test: ``` panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation...

@mologie Did you still got this error: ``` panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0xb6da5e] goroutine 2416337 [running]: capnproto.org/go/capnp/v3/rpc.(*Conn).handleCall.func4.6() capnproto.org/go/capnp/[email protected]/rpc/rpc.go:952...