Is your feature request related to a problem? Please describe.
Regressions is hard to avoid when expanding features of an application.
Describe the solution you'd like
We should watch for regressions in performance through use of CI (does not need to be github hosted).
CI step to profile master branch should look for improvements and regressions in performance. This would also serve as integration testing, which has been a minor issue in the repository (i.e duplicate flags are not noticed on compile time and needs to be triggered as an error on runtime)
Describe alternatives you've considered
None
Additional context
https://go.dev/blog/pprof
https://hackernoon.com/go-the-complete-guide-to-profiling-your-code-h51r3waz
https://dave.cheney.net/2013/06/30/how-to-write-benchmarks-in-go
Is your feature request related to a problem? Please describe.
Regressions is hard to avoid when expanding features of an application.
Describe the solution you'd like
We should watch for regressions in performance through use of CI (does not need to be github hosted).
CI step to profile master branch should look for improvements and regressions in performance. This would also serve as integration testing, which has been a minor issue in the repository (i.e duplicate flags are not noticed on compile time and needs to be triggered as an error on runtime)
Describe alternatives you've considered
None
Additional context
https://go.dev/blog/pprof
https://hackernoon.com/go-the-complete-guide-to-profiling-your-code-h51r3waz
https://dave.cheney.net/2013/06/30/how-to-write-benchmarks-in-go