On Nov 21, 2007 12:00 PM, Michelle Cox <mcox@charter.net> wrote:
> 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?

I have the same question. Does the number of modules enabled
significantly affect memory usage?

Not only memory, but loading time. The php include_once() that is used to load modules is an expensive operatin.

Both can be remedied (to a large degree) by using an op-code cache that caches in memory (such as what APC does by default, others require certain config options).

There is an article on 2bits coming up soon on details. Stay tuned.

I tend to create tons of tiny modules, many of which do something
simple - like provide a single hook. If the overhead from this
approach is significant, then I need to change my ways!

Ryan

>
> Michelle
>
> On 11/21/2007 12:29:46 PM, Khalid Baheyeldin ( kb@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@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@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
> >
>
>