C function profiler

[vbraun]

This ticket complements the %prun magic for Python profiler with a %crun magic that given C function profile information using gperftools (optional, expected to be provided by the OS).

Component: performance

Author: Volker Braun

Branch/Commit: 29db6cd

Reviewer: Nathann Cohen

Issue created by migration from https://trac.sagemath.org/ticket/16038

[vbraun]

Branch: u/vbraun/c_profiler

[nathanncohen]

Commit: 8dd0d7d

[nathanncohen]

comment:2

(DEAD curious)

---

New commits:

86fe787	fix sage -gdb
234b6c9	Do not import prun, it is provided by IPython
8dd0d7d	initial implementation of a gperftools profiler interface

[sagetrac-git]

Changed commit from 8dd0d7d to 3f98bd0

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

3f98bd0

seach for alternatively-named pprof binaries

[nathanncohen]

comment:4

Helloooooooooo !!!

It would be cool to have an explicit error message when there is no output due to this 10ms thing. Could you also add this new file to the reference manual ?

By the way, what it this :param s:/:type s: ? I never saw them before. Could you wrap that in a "INPUT" block btw (the two crun functions need one) ?

Also : the gif output is cool but would there be a way to make it available through %crun directly ? Or at least crun("cmd") ?

There is also an unfinished sentence in the doc :

By default, a if 

Nathann

(super nice tool !)

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. New commits:

f8513e7	improve documentation
1f045f7	add the Sage IPython extension to the manual
acebf36	warn if profiled command finishes < 100ms

[sagetrac-git]

Changed commit from 3f98bd0 to acebf36

[vbraun]

comment:6

Done.

The :param is standard Python syntax which we don't use in Sage. I changed it to our conventions.