Overhead cost of single vs. multiple memcached connections?
perrin at elem.com
Thu May 24 15:16:30 UTC 2007
On 5/24/07, Patrick Galbraith <patg at grazr.com> wrote:
> for memcached. One of the questions that other developers in my
> organisation had was whether instantiating to use multiple connections
> to various memcached servers has much overhead vs. a single connection
> to the memcached server running on localhost
There's no inherent cost to having more than one connection in any
network application. The cost of having memcached on localhost vs. a
remote box is essentially your network latency. Some client-server
apps like MySQL can use pipes when talking to localhost and avoid the
overhead of TCP sockets, but memcached always uses TCP sockets, so
that isn't a factor.
More information about the memcached