Hi,
Another issue with merb caching :) When using memcached store,
merb::cache doesn't seem to close connections to the memcached server.
Even stranger, connections don't seem to be getting reused, rather a
new connection to memcached server gets created on every cache access.
I've an api service running as a merb application. I use a threaded
client that makes, say 200 simultaneous requests to the the app. For
each request, the merb app tries to provide the results from cache and
accesses database only if its a cache miss. On each client execution,
the number of open file descriptors (memcached socket connections)
goes up by 200. Eventually, after a few executions, the open file
descriptor limit on the server is crossed and memcached returns a
EMFile error ("too many open files"), or sometimes even a
"ATimeoutOccured" exception.
It's already logged as a ticket but there hasn't been any activity or
comments thereafter.
https://merb.lighthouseapp.com/projects/7588/tickets/219-merbcache-opens-too-many-connections-to-mecached
There is just one comment suggesting to dispense with merb::cache and
use memcached gem directly. I tried even that, but unfortunately,
calling @cache.quit doesn't seem to be closing the connection and the
number of open file descriptors keep on moving northwards for me. I'm
on Ubuntu jaunty using Merb 1.1, memcached 1.2.5 and memcached gem
0.15.3. Any help will be highly appreciated.
thanks
Amit
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---
