using connection pool

98 views
Skip to first unread message

ktechie

unread,
Nov 24, 2011, 8:19:55 AM11/24/11
to xmemcached
In our application I am using a connection pool.

There are 2 App Servers and 2 memcached servers. The size of
connection pool is 50. Which means there will be 50 connections from
each App Server to each memcached Server.

What are the drawbacks of having a large connection pool.

There is a connection timeout of 1 minute. Is this 1 minute of
inactivity?

After 1 minute will it need to create a connection afresh?

dennis zhuang

unread,
Nov 24, 2011, 9:34:21 PM11/24/11
to xmemc...@googlegroups.com
I don't think you must have a so large connection pool for your connection.In my experience, connection pool didn't improve better performance in most common situations.I recommend you to get a benchmark between pool and default configuration with you app.

The connect time is the timeout for connecting memcached.It doesn't mean the inactivity of the connection,so you don't need to create a connection afresh any more.



2011/11/24 ktechie <kirandos...@gmail.com>

--
You received this message because you are subscribed to the Google Groups "xmemcached" group.
To post to this group, send email to xmemc...@googlegroups.com.
To unsubscribe from this group, send email to xmemcached+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/xmemcached?hl=en.




--
庄晓丹
Email:        killm...@gmail.com
伯岩(花名)  bo...@taobao.com
Site:           http://fnil.net

淘宝(中国)软件有限公司 / 产品技术部 / Java中间件

Reply all
Reply to author
Forward
0 new messages