On 3/20/07, <b class="gmail_sendername">Scott Hadfield</b> <<a href="mailto:hadsie@gmail.com">hadsie@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi All,<br><br>I've been thinking about a possible summer of code idea, but I'm not sure it will fly so I wanted to get some feedback.<br><br>The basic idea is to look into solutions for running Drupal simultaneously across multiple servers for the purposes of running extremely large/busy sites, for load balancing on multiple servers (both database and web servers), or just for high availability (if one server dies, another will kick in). The project would consist of developing and documenting ways that this can be accomplished and developing tools or other Drupal patches/modules that are needed to accomplish the various tasks.
<br><br>One of the main problems with this as a SoC proposal is that a large majority of what needs to be done here is OS/web server/database server specific. There would probably be a lot of Drupal specific stuff, but I'm not sure exactly how much.
<br><br>Even if this won't fly as a SoC project I am still be interested on working on this. What's already been done in this area? Maybe some of this has already been solved?<br><br>Thanks for any feedback,<br><span class="sg">
Scott
</span></blockquote></div><br>Scott<br><br><a href="http://Drupal.org">Drupal.org</a> already runs on 2 web servers + 1 db server, so the underpinnings are there.<br><br>Yes, it involves a lot of tuning of the LAMP stack. See here
<br><a href="http://2bits.com/articles/drupal-performance-tuning-and-optimization-for-large-web-sites.html">http://2bits.com/articles/drupal-performance-tuning-and-optimization-for-large-web-sites.html</a><br><br>However, it also involves finding and eliminating bottlenecks in modules (upcoming article
<br>in the above series). These are definitely code changes, and should be contributed as patches. Offending modules that do not scale well are locale and statistics in core, as well as many in <br>contrib (e.g. gsitemap)
<br><br>I would be interested in mentoring such a project, although a multi server setup is not <br>something I have available. I can provide limited access to a very large Drupal site though<br>(half a million page views per day).
<br>-- <br><a href="http://2bits.com">2bits.com</a><br><a href="http://2bits.com">http://2bits.com</a><br>Drupal development, customization and consulting.