benchmark tests as part of the CI

[esigo]

Is your feature request related to a problem?
It is hard to overstate the importance of benchmarking and monitoring the benchmarks over time. This becomes even more important to us as it is expected/desired that telemetry operations should have minimal adverse impact on performance. In order to quantify and measure how well we're doing there, benchmark tests have to be added as part of the CI.

Describe the solution you'd like

This can be done using continuous-benchmark where benchmark results can be stored on every merge to the main branch. To avoid noising the main branch, gh-pages branch can be used to push the benchmark results. This has already been used in python SIG.

Tasks which require privilege:

• Activating githbub-pages
• Creating gh-pages branch

Describe alternatives you've considered
Which alternative solutions or features have you considered?

Additional context
Add any other context about the feature request here.

[esigo]

This can be assigned to me.

[esigo]

The graphs for the benchmark tests we already have in the repo can be found here

[lalitb]

Please see if this is what is required:

[esigo]

Thanks @lalitb, yes it is.