tag:blogger.com,1999:blog-3958623046725572438.post1288352698399060926..comments2008-09-03T08:43:54.351-05:00Oldaghttp://www.blogger.com/profile/14242449133322470801noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3958623046725572438.post-5340427845189283962008-09-03T08:43:00.000-05:002008-09-03T08:43:00.000-05:00I, unfortunately, do not. I work on the centralized monitor server and not the proxy specifically.<BR/><BR/>However, according to our proxy devs, this memory is way out of line with what we expect. Could you open a bug report at bugs.mysql.com?Oldaghttp://www.blogger.com/profile/14242449133322470801noreply@blogger.comtag:blogger.com,1999:blog-3958623046725572438.post-56505185650483550722008-09-03T08:07:00.000-05:002008-09-03T08:07:00.000-05:00Do you have any stats about memory usage? We used proxy in production and had a program automatically restart proxy when it used more than 512 Mb; the lua script was a failover/failback script, used with 18 persistent connections (so never more than that active -- we had a proxy instance live on each webserver, so the webservers could just connect to localhost, and so resource usage would be spread across many machines). Memory usage fluctuated wildly, often it was under 256 Mb, and the characteristics did not speak to a memory leak (it would go up to, say, 400 Mb, then drop down, etc)....but once a day or more the memory usage was high enough to need to restart proxy. 1/2 Gb of memory was too much usage for a proxy, so we got rid of it.Sheeri K. Cabralhttp://www.blogger.com/profile/13990877688502800403noreply@blogger.com