Domenic - (and others please!)<br><br>do you have any tools or methods that you could share for profiling drupal sites? thanks!<br><br>-Benj<br><br><div class="gmail_quote">On Thu, Mar 5, 2009 at 1:11 PM, Domenic Santangelo <span dir="ltr"><<a href="mailto:domenic@workhabit.com">domenic@workhabit.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Thu, Mar 5, 2009 at 9:26 AM, Dave Maddox <<a href="mailto:davesoftdes@gmail.com">davesoftdes@gmail.com</a>> wrote:<br>
> Thoughts on Drupal problem solving (no real fix for Sam here, sorry):<br>
</div><good stuff snipped><br>
<br>
To bring what Dave said into the realm of actionable steps, I've found<br>
code profiling to be immensely helpful in diagnosing strange<br>
performance problems. You might discover some really interesting<br>
things -- a couple months ago I found that a high-traffic page on a<br>
client site was module_invoke'ing hundreds and hundreds of times and<br>
bogging that page down big time because of it. Issues like that only<br>
get bigger the more modules you've got, and they had a TON. Turns out<br>
it was some legacy code that wasn't even doing anything anymore (!)<br>
except for taking up a bunch of CPU cycles.<br>
<br>
Point being, some standard development/performance practices (like<br>
code profiling) can help a lot, especially when recurring costs need<br>
to be low. In startup land, a few dev days optimizing code is often<br>
much more feasible than throwing more hardware at it.<br>
<font color="#888888"><br>
-D<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
<a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
</div></div></blockquote></div><br>