By ioo on

I mean they are not CHECKED off, they are just there... should I remove them from the server? Does it show down the site?

Thanks!

Comments

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

If you really don't need them (and they are not CORE modules), you should remove them (and save them for later),

Even unloaded modules create some overhead and can slow down your site. So it's good practice to remove unwanted modules. It is best practice to keep a test site which might have all modules, and just load the opnes you use to the live site.

See also http://drupal.org/best-practices

--
http://ken.blufftontoday.com/
Search first, ask questions later.

dman’s picture

dman commented

Isn't the only overhead just when you actually visit the admin/modules page?

The rest of the time they are dead files, and about as troublesome as having a lot of unused files sitting around in any other directory.
How do you think disabled modules affect a running site? /modules/* is only listed on request, not for each page.

.dan.

http://www.coders.co.nz/

.dan. is the New Zealand Drupal Developer working on Government Web Standards

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

Dan-

[post revised after my brain kicked in]

I was thinking of the PHP memory limit setting change that you sometimes have to do if you have X modules installed

http://drupal.org/node/29268

My understanding based on that was that best practice was to remove all "unused" modules from your proiduction server.

Is there anything new in the Handbook on this topic?

--
http://ken.blufftontoday.com/
Search first, ask questions later.