On Sep 28, 2:10 pm, weaselkeeper <[email protected]> wrote:
> We've found that the memcached gem for rails has some issues when > memcached nodes drop offline, How has a different server helped here. Have any bugs been filed in the memcached gem you were using? I'd love to get those problems fixed. > and are also limited to <1MB objects. Since some of our customers want > to use memcached for larger > objects (images mostly) that limitation was a bit of a problem. This > doesn't reflect on memcached per se > of course. But we found it expedient to go to a vendor, rather than > work on the problem ourselves. It's a constant that's defined in a header file and is trivial to change. It's basically there as a rule of thumb. If you want something bigger, you're likely doing something wrong. For example, if you're trying to cache images for a site, you should *probably* be using squid or varnish or cloudfiles or something similar as your caching tier which will yield you *far* greater scalability and performance. But if you want to use memcached for it and the 1MB barrier hits you, it's still just a number that exists in one place. I suppose we could even make it a configure option, though it's rare that anyone approaches 1MB without there being a better solution to their problems.
