the change introduce a performance regression? If so, it will be good to measure the impact using benchmarks. • If the change is substantial or is a breaking change, you must publish the proposal as an issue of design docs for some sections of Vitess Benchmark description: Design docs related to the benchmarks of Vitess arewefastyet description: Nightly Benchmarking project for Vitess Background With through a set of benchmarks divided into two categories: micro and macro, the former focuses on unit-level functions, and the latter targets system-wide performance changes. Those benchmarks are run every

the change introduce a performance regression? If so, it will be good to measure the impact using benchmarks. • If the change is substantial or is a breaking change, you must publish the proposal as an issue of design docs for some sections of Vitess Benchmark description: Design docs related to the benchmarks of Vitess arewefastyet description: Nightly Benchmarking project for Vitess Background With through a set of benchmarks divided into two categories: micro and macro, the former focuses on unit-level functions, and the latter targets system-wide performance changes. Those benchmarks are run every

the change introduce a performance regression? If so, it will be good to measure the impact using benchmarks. * If the change is substantial or is a breaking change, you must publish the proposal as an issue

the change introduce a performance regression? If so, it will be good to measure the impact using benchmarks. • If the change is substantial or is a breaking change, you must publish the proposal as an issue

the change introduce a performance regression? If so, it will be good to measure the impact using benchmarks. • If the change is substantial or is a breaking change, you must publish the proposal as an issue