Investigate using Hyperfine in benchmark scripts

[jqnatividad]

The current benchmark script has been improved, but it still lacks the rigor of a proper benchmark.

Investigate using hyperfine, and perhaps, we can even automate the benchmarks as part of the release process.

[github-actions]

Stale issue message

[udsamani]

@jqnatividad Let me know if this is being worked upon ? Or I can pick this up !

[jqnatividad]

Hi @udsamani , @minhajuddin2510 just started working on it, but there's more stuff on the backlog he can work on.

So yeah, have a go!

[jqnatividad]

Also, NYC's 311 data is a very interesting dataset, and I'd like to keep it as the reference benchmark data.

But it'd be great if we parameterize the benchmark data so folks have the option to change it, and perhaps, maintain their own internal benchmarks using data that's more representative of their data workloads/pipelines.

https://github.com/jqnatividad/qsv/blob/master/docs/PERFORMANCE.md#benchmarking-for-performance

[jqnatividad]

Hi @udsamani , just checking to see if you have any questions about the old benchmark script...

[jqnatividad]

With #542, we'll stick with the benchmark script, just making sure it runs the latest version of qsv, and just run the benchmark manually on release.

Will revisit using hyperfine in the future when we attempt to integrate automating benchmark generation as part of the release process, and adding wontfix tag for now...

[github-actions]

Stale issue message

[jqnatividad]

reopening and removing wontfix as we add this back to the backlog

[jqnatividad]

Finally implemented by @minhajuddin2510 in #1237