[development] How many modules is too many?

[Michelle Cox]

I have nearly 100 projects, many with multiple modules, and am not done 
adding, yet. It does really eat up memory like crazy but I haven't heard a 
solution to it. The fact is that some sites, especially social networking 
ones, use a lot of modules. Most of them are fairly small but needed. Would 
combining the smaller modules into one big one help any? Or would that still 
use the same amount of memory?

Michelle

On 11/21/2007 12:29:46 PM, Khalid Baheyeldin (kb at 2bits.com) wrote:
> (Changing the subject)
>
> I regularly see 80+ to 110+, and that causes Apache to eat 100MB per
> process, which is really not good ...
>
> This is the open buffet binge syndrome detailed here:
>
> http://2bits.com/articles/server-indigestion-the-drupal-contributed-
> modules-open-buffet-binge-syndrome.html
>
> On Nov 21, 2007 12:50 PM, Jim Li <jimmydami at gmail.com> wrote:
>
> > Cool, thanks!
> >
> It'd be interesting to have a poll on how many modules people use on a
> > social network site. I heard someone uses 160 modules at his dev site,
> > it may go down a bit later, but it probably will still in the 100+
> > ragnge :)
> >
> > On Nov 20, 2007 6:31 PM, Earl Miles <merlin at logrus.com> wrote:
> > > On the other hand, having 150+ modules load *is* going to eat a whole
> > > lot of memory; so actually activating all these modules is a really 
> > > bad
> > > idea.
> > >
> > > And yes, the modules page under 4.7 is going to choke like [insert
> > > really bad sports team metaphor here].
> > >
> > >
> > > Sean Robertson wrote:
> > > > As I understand it, Drupal 5+ no longer does that.  That's
> what the
>