(Changing the subject)<br><br>I regularly see 80+ to 110+, and that causes Apache to eat 100MB per process, which is really not good ...<br><br>This is the open buffet binge syndrome detailed here:<br><br><a href="http://2bits.com/articles/server-indigestion-the-drupal-contributed-modules-open-buffet-binge-syndrome.html">
http://2bits.com/articles/server-indigestion-the-drupal-contributed-modules-open-buffet-binge-syndrome.html</a><br><br><div class="gmail_quote">On Nov 21, 2007 12:50 PM, Jim Li <<a href="mailto:jimmydami@gmail.com">jimmydami@gmail.com
</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Cool, thanks!<br>It'd be interesting to have a poll on how many modules people use on a
<br>social network site. I heard someone uses 160 modules at his dev site,<br>it may go down a bit later, but it probably will still in the 100+<br>ragnge :)<br><div><div></div><div class="Wj3C7c"><br>On Nov 20, 2007 6:31 PM, Earl Miles <
<a href="mailto:merlin@logrus.com">merlin@logrus.com</a>> wrote:<br>> On the other hand, having 150+ modules load *is* going to eat a whole<br>> lot of memory; so actually activating all these modules is a really bad
<br>> idea.<br>><br>> And yes, the modules page under 4.7 is going to choke like [insert<br>> really bad sports team metaphor here].<br>><br>><br>> Sean Robertson wrote:<br>> > As I understand it, Drupal 5+ no longer does that. That's what the
<br>> > .info files are for. Those files are only a couple hundred bytes each<br>> > so the full page even with a ton of modules downloaded should only use a<br>> > small amount of memory unless you enable them all (which would affect
<br>> > all pages, not just that one).<br>> ><br>> ><br>> ><br>> > Jim Li wrote:<br>> >> Hello,<br>> >><br>> >> I saw some complaints that admin/build/modules page loads all modules
<br>> >> and eats up lots of memory. And I heard a story that somebody new to<br>> >> drupal was trying to evaluate >150 modules and eventually drupal<br>> >> 'crashed' on this page due to memory limit. So I am just wondering is
<br>> >> it a good idea that we use tabs to separate module groups on<br>> >> admin/build/modules page? Will it help with the problem? We can have<br>> >> three tabs: core, contrib, oh and uninstall (which will need some
<br>> >> speical css rendering).<br>> >><br>> >> Thanks,<br>> >> Jim<br>> ><br>><br>><br></div></div></blockquote></div><br><br clear="all"><br>-- <br>Khalid M. Baheyeldin<br>
<a href="http://2bits.com">2bits.com</a><br><a href="http://2bits.com">http://2bits.com</a><br>Drupal optimization, development, customization and consulting.