<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
We released an amazon ec2 ami with xdebug setup and output for
kcachegrind/wincachegrind, have a look here :
<a class="moz-txt-link-freetext" href="http://www.io1.biz/blogs/drupalxdebugvimkcachegrind-ec2-ami">http://www.io1.biz/blogs/drupalxdebugvimkcachegrind-ec2-ami</a><br>
<br>
<br>
Fintan<br>
<br>
<br>
Darrel O'Pry wrote:
<blockquote
cite="mid:bfcbb6230806290507r137fba2jffddfff38c9876fa@mail.gmail.com"
type="cite">The frequency changes per page that you're loading... but
to set it up you need to install xdebug and setup the profiling..<br>
<br>
<a moz-do-not-send="true"
href="http://onwebdevelopment.blogspot.com/2008/06/php-code-performance-profiling-on.html">http://onwebdevelopment.blogspot.com/2008/06/php-code-performance-profiling-on.html</a><br>
<br>
might be a good starting point for you.<br>
<br>
.darrel.<br>
<br>
<div class="gmail_quote">On Sun, Jun 29, 2008 at 7:39 AM, Marjorie
Roswell <<a moz-do-not-send="true" href="mailto:mroswell@gmail.com">mroswell@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;">Is
that this?<br>
<a moz-do-not-send="true"
href="http://kcachegrind.sourceforge.net/cgi-bin/show.cgi"
target="_blank">http://kcachegrind.sourceforge.net/cgi-bin/show.cgi</a><br>
<br>
I seriously wouldn't have a clue how to get that running.<br>
<br>
If it's easy for you, can you release this report? If not, well, 'twas<br>
a good idea, anyhow.<br>
<br>
Margie<br>
<div>
<div class="Wj3C7c"><br>
On Sun, Jun 29, 2008 at 7:09 AM, Robert Douglass <<a
moz-do-not-send="true" href="mailto:rob@robshouse.net">rob@robshouse.net</a>>
wrote:<br>
> XCachGrind makes such reports.<br>
><br>
> Robert Douglass<br>
><br>
> Senior Drupal Advisor<br>
> Acquia<br>
> <a moz-do-not-send="true" href="mailto:robert@acquia.com">robert@acquia.com</a><br>
> +1 517 639 0204 (US)<br>
> +49 228 4097 197 (Germany)<br>
><br>
><br>
><br>
> On Jun 29, 2008, at 1:04 PM, Marjorie Roswell wrote:<br>
><br>
>> I'm on a drupal learning curve.<br>
>><br>
>> It occurs to me that I'd love to see a report of all the
functions<br>
>> used in Drupal by frequency. (Then, I'd tackle the learning
curve by<br>
>> starting with what's used most, and moving down the list!)<br>
>><br>
>> I imagine starting with something like the api pull from the
Module<br>
>> Builder Module (<a moz-do-not-send="true"
href="http://drupal.org/project/module_builder" target="_blank">http://drupal.org/project/module_builder</a>)
and then<br>
>> somehow scanning the CVS for all the functions, and
calculating a<br>
>> frequency.<br>
>><br>
>> Seriously, would love to basically tackle this learning curve
in a<br>
>> logical way, based on how often something appears in code,
ideally in<br>
>> both core and contrib, combned.<br>
>><br>
>> I recognize that little-used code functions may still be quite<br>
>> important, but this approach would certainly serve as a good
guide.<br>
>><br>
>> I don't have the skillset to write this report. Is there
anyone for<br>
>> whom producing this function frequency report would be a
relative<br>
>> cinch?<br>
>><br>
>> Margie<br>
><br>
><br>
</div>
</div>
</blockquote>
</div>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Fintan Galvin
Managing Director
IO1 Limited
Leveraging Strategic Advantage
Mobile: +44 773 8506781
Ph: + 44 20 8816 7690
skype: johnfgalvin
********************************************************************
Important.
Confidentiality: This communication is intended for the above-named person(s) and may be confidential and/or legally privileged.
Any opinions expressed in this communication are not necessarily those of the company. If it has come to you in error you must
take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender immediately.
********************************************************************</pre>
</body>
</html>