I'm working on a tool to bisect through a git history to find performance changes to a given benchmark.
Unlike a traditional git bisect
, which looks for a boolean change, we want to find points at which a value has a sharp jump.
=> More informations about this toot | More toots from john@hawthorn.pub
For comparison above is a graph with 50 points vs below measuring 300 points at a regular interval (it has a slightly different X axis... I made a mistake). I think the old version looks better but the new version was way faster to generate and it more precisely narrows down the specific commit(s) which caused a change (rather than an interval, which I'd then have to bisect).
=> More informations about this toot | More toots from john@hawthorn.pub This content has been proxied by September (3851b).Proxy Information
text/gemini