On 8/30/07, <b class="gmail_sendername">Earl Miles</b> <<a href="mailto:merlin@logrus.com">merlin@logrus.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;">
<br>I'm a lot more interested in the time it takes to bootstrap Drupal than<br>I really am in how much memory we use, though. Loading code is one of<br>the biggest timesinks in Drupal right now, and I think in Drupal 7 we'll
<br>want to try to move even further into the realm of making code optional.<br>There is no reason that very simple pages can't run in 30ms, except that<br>we generally spend 70ms (even on fast machines) loading code (let alone
<br>actually generating a page).<br></blockquote></div><br>Loading less code is always a good thing, but on a good dedicated server<br>with op-code caches, it is a diminishing returns situation, and the database<br>becomes the bottleneck rather than code.
<br><br>Here are examples from a typical page load, for an authenticated user (hence <br>no caching). The queries come from MySQL's query cache, and hence the <br>short time. But, the entire page including the blocks, ...etc. takes ~60ms.
<br><br>Executed <em>121</em> queries in <em>22.04</em> milliseconds. Page execution time was <em>82.45</em> ms.<br clear="all">Executed <em>120</em> queries in <em>26.54</em> milliseconds. Page execution time was <em>85.98
</em> ms.<br><br>I am not invalidating your point: shared hosts need the code optimization.<br>Not only for speed, but memory footprint per process. But for dedicated? <br>Far less so.<br><br><br><br>Back to memory: can people try to replicate these results on both bloated
<br>sites and simpler ones?<br><br>Also, how do we make memory measurement patchless (part in core, need<br>Dries' blessing on this, and part in Devel).<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.