Steven Grimm wrote:
>
> In addition, you might want to compare the single-threaded memcached
> 1.2.2 with the same version compiled as a multi-threaded app, but run
> with "-t 1" so that it only uses one thread. That will tell you how much
> overhead is introduced by the threading infrastructure itself (acquiring
> locks, etc.) without any possibility of resource contention affecting
> the results.
Wouldn't it also make sense to compare the threaded version against
running n instances of the unthreaded version where n= the number of
CPUs available?
--
Les Mikesell
[EMAIL PROTECTED]
