-
Notifications
You must be signed in to change notification settings - Fork 450
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for > 1 MB of data #54
Comments
It's doubtful I will accept this as caching values this large has always struck me as a design smell. Your application design is probably questionable if you are caching values this large. On a side note, you can enable compression to get larger values, assuming your values are compressible. |
OK, you have certainly the right to make your software "opinionated" and I respect your choice. To clarify my opinion - I am used to work with software, which "... was not designed to stop its users from doing stupid things, as that would also stop them from doing clever things". Note also, that in the second patch will dalli automatically query the actual limit of the server. In a case, where the user intentionally configured his memcached to support larger values, will unpatched dalli incorrectly report, that memcached is limited to 1 MB - that's clearly a bug in my opinion. |
Support greater than 1MB values, closed by 55def36 |
I'd like to see a support for data values bigger than 1 MB, memcached can already be configured (using the "-I" option) to enable it. I propose the following alternative patches which add the support to dalli. In the first one is the value set by user, in the second we find out the value in runtime. They were tested with memcached-1.4.4.
Set by user:
Runtime check:
The text was updated successfully, but these errors were encountered: