feat: add autocannon-compare-cli package

[guilhermelimak]

Add a small cli utilty to compare autocannon results.

You can see a preview of the comparison here:

Closes nearform/hub-draft-issues#172

[github-actions]

No linked issues found. Please add the corresponding issues in the pull request description.
Use GitHub automation to close the issue when a PR is merged

[simoneb]

@codeflyer @simone-sanfratello can you please take a look?

[simone-sanfratello]

Nice! I'd add the option to rename the columns, sometimes it's hard to remember which one is "a" and which one is "b" and it's convenient to have for example "current" and "next"

autocannon-compare-cli -a ./path-to-file-a.json -b ./path-to-file-b.json -a-as current -b-as next

[simoneb]

Shall we include using this in the Web UI then?

[guilhermelimak]

Shall we include using this in the Web UI then?

I think that's a good idea. Should make it way easier to use it that way.

[simone-sanfratello]

Shall we include using this in the Web UI then?

That was my original request! 🚀

[guilhermelimak]

I've updated the backend with a new route to return the new comparison, but the frontend changes are still missing.

[guilhermelimak]

This now is partially implemented on the frontend, it's using the new route and showing the results in a table but could use some improvements on styling like adding color to the results.

I kept the old compare route intact and created a v2 using the new compare function. I'm not entirely sure if we should try to integrate both the new and old results since they carried some different info on them. If that's not desirable we could just remove the old one and remove the v2 naming from the new one.

[simoneb]

@guilhermelimak where do we stand with this PR?

[guilhermelimak]

@simoneb should be ready for reviewing and testing, there's the point I mentioned on my previous comment about some data we had on the previous compare function and we don't have on the new one but should be good to go if that's fine