On 9/24/10 12:10 AM, Paul Lindner wrote:
A good rule of thumb is one thread per core, but you should run your
own benchmarks on your hardware.
+1
This is a good general rule of thumb overall, though the old general
rule is go up to 4x number of CPUs if tuning for throughput, and just at
or slightly below if tuning for latency. You'll get both pretty well
OOTB with one thread per core.
However I can pretty much guarantee you'll run into other bottlenecks
before you have to worry about your CPU usage.
Likely network.
On Thu, Sep 23, 2010 at 11:59 PM, manoher tadakokkula
<[email protected] <mailto:[email protected]>> wrote:
one more question, what is the recommendation for number of worker
threads for single-core and dual-core systems ?
-manoher
On Wed, Sep 22, 2010 at 8:37 PM, Trond Norbye
<[email protected] <mailto:[email protected]>> wrote:
The last thread is the thread running the clock and accepting
new connections.
Cheers
Trond
Sent from my iPhone
On 22. sep. 2010, at 16:50, Paul Lindner <[email protected]
<mailto:[email protected]>> wrote:
memcache only compiles in a threaded mode these days. The
docs are out of date.
The 5th thread you see is probably a supervisor, the other 4
are worker threads.
On Wed, Sep 22, 2010 at 6:30 AM, manoher tadakokkula
<[email protected] <mailto:[email protected]>> wrote:
Hi,
I am trying to compile source to install memcached. i
have a dual-core system.
when i did ./configure && make && make install , i think
it is installing threaded version.
Running memached daemon shows, pstree displays as
5*memcached.. hence i think its running 5 threads..
My questions are :
Docs file threads.txt says, by default it is compiled as
single-threaded appication, how come i got threaded version?
how can i compile the source without threads ?
In threaded version , why am i seeing 5 threads? Docs say
-t default value is 4 , what am i missing ?
thanks in advance,
Manoher T
--
Paul Lindner -- [email protected] <mailto:[email protected]>
-- linkedin.com/in/plindner <http://linkedin.com/in/plindner>
--
Paul Lindner -- [email protected] <mailto:[email protected]> --
linkedin.com/in/plindner <http://linkedin.com/in/plindner>
