We've run into this exact same issue and narrowed it down to the NIC,
but don't really know where to go from there. I'm going to look up
Dormando's suggestions but if anyone else has experience with this and
can point us in the right direction, it would be greatly appreciated.
Thanks,
Jay
On
This is a bit complicated and I still don't understand it fully, but here
are few pointers. BTW all that follows has nothing specific to memcached.
1) cat /proc/interrupts
This will show the list of which core(s) are handling the interrupts for
given devices.
Check eth0/eth1 whichever you
It's a big topic, here's the stuff to google:
- cat /proc/interrupts - look for eth0, eth1, etc. If you have one
interrupt assigned to eth0, you have a single-queue NIC.
If you have many interrupts that look like eth0-0, eth0-1, etc, you have
a multi-queue NIC. These can have their interrupts
Hi
We have an 2 x quad core server with 32 gb ram. If many clients
connect to this server (only memcached runs on it) the first core run
to nearly 100 % use by si (software interrups) and so some client
can't reach the server.
Memcached runs currently with 4 threads and with version (1.4.2). All
We have an 2 x quad core server with 32 gb ram. If many clients
connect to this server (only memcached runs on it) the first core run
to nearly 100 % use by si (software interrups) and so some client
can't reach the server.
Memcached runs currently with 4 threads and with version (1.4.2). All
