The best option is to have a connection pool, and yes, it's faster than doing a new connection every time. There's noticeable overhead if you have a ridiculous amount of servers or clients, but that's not something most people will ever encounter. I think most clients implement connection pooling, and I know Dustin's Java client even takes it one step further with a request merger that allows it to have a single connection to all servers. Which client are you using?
/Henrik On Tue, Jan 20, 2009 at 11:22, Jonathan Ariel <[email protected]> wrote: > Hi all! > Just wondering if on a high traffic website it's better to have or not > persistent connections. > Is there any recommendation? Is there any cost on leaving connections open? > Is it less than opening them on every request? > > Thanks, > > Jonathan >
