Hi! I have a largeish gambit application. It's interpreted under gsi, and is taking up around 25% of my dual core laptop. I would like to profile to see what functions are taking up all the time. How can I do this? (Searching for profiling in the gambit documentation brings up stuff focused on how to profile scheme code that has been compiled to C, but not on profiling of interpreted code.)
Thanks!
Afficher les réponses par date
Check out for Guillaume Germain's statprof profiler.
-- David
Le 09-05-31 à 08:31, lowly coder lowlycoder@huoyanjinjing.com a écrit :
Hi!
I have a largeish gambit application. It's interpreted under gsi, and is taking up around 25% of my dual core laptop. I would like to profile to see what functions are taking up all the time. How can I do this? (Searching for profiling in the gambit documentation brings up stuff focused on how to profile scheme code that has been compiled to C, but not on profiling of interpreted code.)
Thanks! _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
How does ##container->path and ##container->file differ? 0.2 of the stat profiler (aimed at 4.0?) uses ##container->file, grepping through the 4.4.2 source, it seems to be an internal in _guide.scm; however, ##container->path is available. When I replace ##container->file with ##container->path, nothing bad appears to happen.
Also, did "display" change between 4.0 and 4.4 of gambit? Stat-profiler seems to assume that it does some type of flattening of lists, (and as a result the 'HTML" code is generates is stuck in abunch of lisp lists, and I had to do some ugly hacks to make it raw HTML).
Thanks!
On Sun, May 31, 2009 at 4:52 PM, David St-Hilaire <sthilaid@iro.umontreal.ca
wrote:
Check out for Guillaume Germain's statprof profiler.
-- David
Le 09-05-31 à 08:31, lowly coder lowlycoder@huoyanjinjing.com a écrit :
Hi!
I have a largeish gambit application. It's interpreted under gsi, and is taking up around 25% of my dual core laptop. I would like to profile to see what functions are taking up all the time. How can I do this? (Searching for profiling in the gambit documentation brings up stuff focused on how to profile scheme code that has been compiled to C, but not on profiling of interpreted code.)
Thanks! _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
When I replace ##container->file with ##container->path, nothing bad appears to happen.
"When it's not broken, do not try to fix". (Which actually is a good moto *only* if the code was initially clean. Otherwise, Refactoring should happen ASAP to avoid being damned and cursed by next people who will maintain your code.That's why I personally think of forcing myself to do test-driven development.)
Also, did "display" change between 4.0 and 4.4 of gambit? Stat-profiler
I think Marc recently fixed a "bug" in DISPLAY, where printing was inconsistent with other implementations or something like that. That has been said on that list less than a month ago iirc.
P!
On Monday, June 1, 2009 at 12:11:18 (+0900), Adrien Piérard wrote:
When I replace ##container->file with ##container->path, nothing bad appears to happen.
"When it's not broken, do not try to fix". (Which actually is a good moto *only* if the code was initially clean. Otherwise, Refactoring should happen ASAP to avoid being damned and cursed by next people who will maintain your code.That's why I personally think of forcing myself to do test-driven development.)
I've been using statprof with this fix for a couple of weeks, and everything works fine.
Also, did "display" change between 4.0 and 4.4 of gambit? Stat-profiler
I think Marc recently fixed a "bug" in DISPLAY, where printing was inconsistent with other implementations or something like that. That has been said on that list less than a month ago iirc.
Just replace display by print and it will give the expected result.
Vincent
-
Adrien Piérard -
David St-Hilaire -
lowly coder -
Vincent St-Amour