Skip to content
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

Closed
markjaquith opened this issue Apr 30, 2013 · 3 comments
Closed

Give Memcache daemon more memory #70

markjaquith opened this issue Apr 30, 2013 · 3 comments

Comments

@markjaquith
Copy link
Contributor

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

@TheLastCicada
Copy link
Contributor

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?

@jeremyfelt
Copy link
Member

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.

WybrenKoelmans pushed a commit to WybrenKoelmans/VVV that referenced this issue May 2, 2019
)

# Conflicts:
#	config/theme-options.php
#	header.php
@lock
Copy link

lock bot commented Feb 24, 2020

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.

@lock lock bot locked and limited conversation to collaborators Feb 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants