Multiple nodes vs multiple servers
Martijn van Zal
mzal at brothersinart.com
Tue May 8 22:53:01 UTC 2007
I guess it depends on the amount your application relies on it. If you use a
couple of instances (which most people seem to do) you can update them one by
one, without your databases getting the full load all at once.
It will cost you a couple of connects though, and a get_multiple is not as
easy as with 1 instance.
Martijn van Zal
Brothers in art
From: memcached-bounces at lists.danga.com
[mailto:memcached-bounces at lists.danga.com] On Behalf Of Jehiah Czebotar
Sent: woensdag 9 mei 2007 0:04
To: a f
Cc: memcached at lists.danga.com
Subject: Re: Multiple nodes vs multiple servers
On 5/8/07, a f <just1coder at yahoo.ca> wrote:
> Ideally, scaling out to many memcached servers (with >1 node) would be
> preferred but for a pilot I am working on building out a memcached box on
> existing server. It has a dual-xeons and 8GB of RAM. Would it be preferred
> to use many instances on that single server or is it possible to have 1
> large instance?
for your scenario; one instance will do just fine. (one instance is
preferred to keep the number of connections down, and so that client
libraries can better optimize multi get requests)
also many on this list (myself included) would recommend you not
"guess" at how much memcached memory space you actually need, but
start with something small like say a few hundred megs of memory
(memcached is really efficient) and grow it as you need while watching
your usage stats.
More information about the memcached