Dnia 2021-03-15, o godz. 10:44:50 Jeremy French <ibi...@gmail.com> napisał(a):
> So it seems like the logical solution would be to create a test that runs a > benchmark and makes sure the benchmark results are within some acceptable > range. I realize that benchmarks are going to differ from machine to > machine, or based on CPU load, etc. Compare old implementation and new one: https://play.golang.org/p/w9giDccrpNa PS. In a CI pipeline, as we do not know exact HW where tests will run tomorrow, we normalize to a known base. Usually crypto/des suits well as the stable unit of speed. Hope this helps, -- Wojciech S. Czarnecki << ^oo^ >> OHIR-RIPE -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/20210316033610.3841d8a7%40xmint.
