ways to fix windsock iterative compile times
rukai opened this issue · comments
It currently takes 3 minutes to do an iterative build of our windsock benchmarks.
Needless to say this is really bad so I'm looking for ways to improve this.
Ideas:
- Remove shotover dependency from benches, will have to duplicate the transform Configs into windsock but should be a significant win.
- #1437 demonstrates that this will be a big win
- Split setup and bencher logic into 2 seperate binaries. The setup can then be compiled in debug mode which should be a win. We can also avoid recompiling one binary if only the other has changed
The first point was mostly addressed by #1441
The second point relies on various unimplemented features in cargo.
So lets abandon this idea unless we find the need to further optimize windsock compile times in the future.