<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dustin Sallings wrote:
<blockquote cite="mid4DB7F391-5267-4909-8FE2-0C8CF024B82E@spy.net"
type="cite"><span class="Apple-tab-span" style="white-space: pre;"></span>A
single connection with a single thread should give you the performance
you need (since that's all that's on the server-side). I could
conceivably run more than one connection per server if there's a
bottleneck in the wire protocol.<br>
</blockquote>
<br>
If you're connecting to a remote host, network round-trips will
dominate the response time. You will definitely see better throughput
with multiple connections, especially if you're requesting small
objects. Even on the local host you might see a marginal benefit.<br>
<br>
Also, there is a multithreaded version of memcached (in Subversion only
for now -- see the "multithreaded" branch -- though at some point I
hope it will become the main version of the code.) We are successfully
using it on a network of 4-core memcached hosts.<br>
<br>
-Steve<br>
</body>
</html>