Regardless of how it handles things internally, I think what you want to
know is "Can it handle more than one client at a time" and the answer is
Yes. It would be pretty useless if it couldn't.
There should be no changes at all to the client for threaded/non-threaded
builds.
2008/10/15 wing <[E
thanks, todd and toru's words give me insight
from todd, does that mean the mencached's "internal logic" is single-
threaded, but the "network/socket" (sending, receiving data) are
"multi-threaded" ?
(sorry, the question may be silly, but i want to have a bit more
detail)
and if memcached is ena
On Oct 14, 11:54 am, Boris <[EMAIL PROTECTED]> wrote:
> Hi all. We are currently using whalin 1.6 client. I was just
> experimenting with what it would take for us to convert to spy. I
> noticed that there exists WhalinTranscoder class, but it seem to only
> work with whalin 2.0 and above. I took
Hi!
FYI, from version 1.3 multi-thread build is going to be default (it
already is in the development branch).
In addition to Todd's reply, if you actually test the performance
between a single thread build and a multi thread build, you will
notice that the performance difference is not so signi
Hi all. We are currently using whalin 1.6 client. I was just
experimenting with what it would take for us to convert to spy. I
noticed that there exists WhalinTranscoder class, but it seem to only
work with whalin 2.0 and above. I took a glance at encoding
implementation in whalin 2 vs 1.6, and th
It's true being single threaded means it will only do one *thing* at
time, but depending on how you look at it - having only one processor
means you'll only be able to process 1 instruction at a time or can it
do more? This is a good read about how we can get more out of a
single processor then j
as we are evaluating to upgrade to 1.2.6, so, is this a critical bug
to 1.2.6 ?
On 10月7日, 上午11時47分, Dustin <[EMAIL PROTECTED]> wrote:
> Er, scratch that -- I think these changes are actually in 1.2.6, but
> the changesets got rewritten so they have different IDs and authors.
>
> (still hates
from
http://www.danga.com/memcached/news.bml
does that mean before "Version 1.2.2", memcached is single-threaded?
and for version 1.2.2+
memcached is still single-threaded unless we build the memcached with
the following option?
./configure --enable-threads
if so, without the above multi-thr
