So I finally found what was wrong with memaslap. I had to do some
benchmarking lately and I realized that the memaslap is creating twice the
number of connections I was asking for, and not sending anything over every
other connection. So if I asked for -T 2 -c 2 -n 1, instead of 4
connections
I am running some tests using memached 1.4.22 over an Intel Xeon E5 (4
sockets with 8 core each, 2 Hyper threads per core, and 4 NUMA nodes) and
running Ubuntu trusty. I compiled memcached with gcc-4.8.2 with default
CFLAGS and configuration options.
The problem is whenever I start memcached
I am running some tests using memached 1.4.22 over an Intel Xeon E5 (4
sockets with 8 core each, 2 Hyper threads per core, and 4 NUMA nodes) andÂ
running Ubuntu trusty. I compiled memcached with gcc-4.8.2 with default
CFLAGS and configuration options.
The problem is whenever I start
Thanks for you response, find my response below:
On Mon, Feb 9, 2015 at 1:39 PM, dormando dorma...@rydia.net wrote:
I am running some tests using memached 1.4.22 over an Intel Xeon E5 (4
sockets with 8 core each, 2 Hyper threads per core, and 4 NUMA nodes) and
running Ubuntu trusty. I
Btw, I already considered avoiding hyper threads and running all server
threads on the same socket (to avoid cross socket latencies and better
cache usage), but it does not seem to be a hardware related problem.
On Mon, Feb 9, 2015 at 4:29 PM, Saman Barghi sama...@gmail.com wrote:
Thanks for
I see, you are right it makes more sense to be a client side problem in
this case. I write a small test program and if the problem still exists I
will get back to you.
Thanks for your help,
Saman
On Mon, Feb 9, 2015 at 4:39 PM, dormando dorma...@rydia.net wrote:
If mc-crusher engages all