Reduce mem requirements for admin/modules [#15253]

On a shared server, I have some sort of limit when it comes to size of PHP script loaded/executed... with enough modules in place on my site, I seem to surpass this limit. Ultimately, I had to begin to remove modules to add new ones just to be able to access the admin/modules page (it would immediately fail to load or simply timeout).

This was also a case of having two sites served from the same Drupal install, so some modules were enabled in one instance but not in the other. Drupal seems to have to load all of them fully before it can even begin to list the enable/disable screen.

Oddly enough, this didn't seem to break the system as far as I could tell, since this is one of the only pages that seemed to load all the modules at once (to get at their descriptions, etc).

It would be nice to see some way of getting to this page that wasn't so memory intensive. It couldn't hurt to have some sort of install profile page--sort of like a phpinfo() for Drupal--that shows what Drupal's execution size is and how close it is to the limit imposed by PHP (if that is actually where the problem lies) as well .

Not sure if this should be a task or feature request instead.

Comments

Comment #1

Steven commented 11 January 2005 at 04:12

The module information is stored inside the .module file as a regular PHP string. If we want to avoid loading the module, we need to embed the string in another way and read it out directly. However, this is not a good idea, as this way you can enable modules which are broken and thus lock yourself out.