-
Notifications
You must be signed in to change notification settings - Fork 848
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
Give Memcache daemon more memory #70
Comments
I think this goes back to our previous discussion of what is appropriate on the 512 MB basic box. If you crank up the RAM of the VM, then 256 or 128 MB makes a lot more sense. Maybe we can set this during provisioning to be 1/8th of the system RAM? That way if you resize your Vagrant, you'll automatically get more cache space to play with. I will preempt you and note that this would easy to do with Puppet (or Salt or Chef). @markjaquith I've been using http://livebookmark.net/journal/2008/05/21/memcachephp-stats-like-apcphp/ to view memcached statistics and have been finding most sites use way less cache space than I anticipated (or initially allocated), making me think 64 MB might be plenty in most scenarios. What has your experience been? |
About to close this with a commit as well. Agreed that 128M seems like the correct value. Would like to continue to discuss possible stats/monitor tools for inclusion at the default URL. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
The Memcache daemon is set up to use 64 MB of RAM. We should consider bumping that to 128 MB so that sites with a lot of cache entries can be fully tested.
see #68
The text was updated successfully, but these errors were encountered: