After discussion with chrismcintosh, I think it would be a good idea if Aegir allowed admins to set the PHP memory limit for each Drupal site through the Aegir UI. Some sites naturally require more memory than others (especially when using ImageCache), while others not as much. The current design requires you to specify it globally for the entire server, which isn't ideal.
Comments
Comment #1
adrian commentedthis is a pretty ridiculous level of configurability at the site level.
it's not really aegir's job to be managing this in my mind.
Comment #2
guypaddock commented@adrian, how else would you recommend the limit be set?
Comment #3
adrian commentedYou can use either the global.inc include to modify this, or using one of the hooks to inject the value into your settings.php file.
I dont think aegir core will ever give you this level of configurability, but it is our hope to be able to provide the API's so it can be contributed in a contrib space. Already now it's not too hard to write a module which alters the node site-form with the extra configuration option, and pass it to the backend for use in your backend module.
Keep in mind that memory limits set in the settings.php will also affect the memory limit of the site being manipulated in drush on the command line, so you will run into out of memory errors on things such as migrations.
Also, from what I understand, the memory limit doesn't mean that all the processes use the same amount of memory. It just means they use UP to that amount of memory. So having a higher memory limit for all the sites doesn't mean that the sites that use less will be using any more than if they had a lower limit.
Comment #4
adrian commentedComment #5
anarcat commentedfaq material