On Wednesday 13 February 2008 06:21:32 [EMAIL PROTECTED] wrote: > Should we perhaps add a performance benchmark to the tests? > > Normalising it to account for hardware variations might be a problem.
That's somewhat difficult, as it's the performance of languages hosted on Parrot that's most important. I profile Rakudo once in a while. If I ever get the time and energy and brains to figure out where the weird Lua segfaults come from, I'll profile it too. If we were really fortunate, someone would write a Parrot runloop that emits callgrind-compatible output, so that we could profile Parrot at the sub and op level with callgrind_annotate. -- c
