Plans for hierarchical profiler

[Daniel Kraft]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

since (besides working out the flaws still present in profiling
anonymous functions -- see my last mail) the next goal is hierarchical
profiling, here are some thoughts about it (basically about the
interface).  Comments welcome!

Basically, I'm thinking about an interactive command-line interface to
explore the call-tree.  (Later, we could also think about generating
some output; like the Matlab HTML; or even gprof/callgrind data for use
with those tools.)

So one would do:

profile on;
...do something...
profile off;
profshow (profile ('info'), 'hierarchical');

And then the user will be presented with all "top-level" calls together
with their times; like:

1: foo, 2s
2: bar, 0.02s
3: operator \, 0.1s

Next, (s)he can choose one of those branches to go down.  Say, type in
1.  Then all direct childs of foo will be shown, as above; maybe also
the 'self' time spent directly at this level:

foo (self 1.5s)
  1: operator *, 0.05s
  2: myfunc, 0.45s

...and so on.  There should (at least) be commands to step down, up,
maybe go back to the root, and exit the tree-explorer.

Does this sound like a reasonable interface?  Or should I do it
different?  How would you like hierarchical data presented?

Note that here again, I will seperate the backend from the interface --
i.e., make __profile_data or possibly a new function return the tree as
Octave data structure, and have profshow.m interpret it and handle the
interactive stuff.  Thus, we can easily change the interface or add new
presentation options.

Yours,
Daniel

- -- 
OpenPGP: 3BA2 3DDB 7758 F010 BDAB 0DCF 527E 79BA A3B5 3998
or use https://safesend.domob.eu/
- --
Done:  Arc-Bar-Cav-Kni-Ran-Rog-Sam-Tou-Val-Wiz
To go: Hea-Mon-Pri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOQCWkAAoJEFJ+ebqjtTmYZYMQALxxM9OJY7VHGhfpkA0h8fIB
J/PoNVyhY6dl/tuFfDXxtf/S0VAB74OMo0f/mX/nryirV+AE+6Kus3CnkfJFwzpF
skeNglN/C+PbwubvaE0mybGPtLCVuSzyWdNEnjvnCZfs5o+f0dkb1W7lrHqY2Oh3
U0b99Uy3l9KMVaY8l4d80DwpZZFcnl15kbYsilO4R+hiE+Ije1yl4wtq/1zDZ666
JJsGu+/hQel+Kl6qSQljW+vNWZkctBolis1etBfJZ1ugzeh0Yh7wvq2IiwRyc/03
LSGwy/acVeUMkotVg3pxkAKRfcec59xbLMzRY/OUnNggeYyPYzAB8tNiQDYHRYyQ
rh1fOC5vob8y+aUqBUuduRdfAt2/5lEcrc5toG9P/JBUnR0ZgQJzLIfqz2fAamrG
RfHWV57RX60Xh8ACbcHgiNCxjKcN1LFMFZbKlppxsUpGSgKa879VqfKZqzicLstO
kYPqKe1FyW4CnAIhl3YqiBz4/sTWklqvNsI5bhBAAWp+dssM41cgrwHF5EdKpUK3
E6KpR3TtjF8EtPBlG+OQuSMBhe5Ok2DrUZb7fswLlCBm8fTvPY/TMTGwFBGc2TI7
JgyXWdWElRAhwWTsfY93pCPmH1MF68iaHrkPDyzBtV+0pYfLCFhNJPVYb3zKJRSH
TYRjHQTMcnHeWY7po9RD
=nPq6
-----END PGP SIGNATURE-----

smime.p7s
Description: S/MIME Cryptographic Signature