I feel as though dune 3.0.3 is thinking a little to long when I am building Coq. For instance, after finishing
dune build for the master Coq repo, and running
dune build again, it takes a couple of seconds to realize that nothing needs to be done. @Rudi Grinberg are you are aware of similar issues? What is the best way to submit such a bug report?
Can you confirm that the situation is better in 2.9.x?
Trying it now, it needs to rebuild the whole thing unfortunately due to the different OCaml version
Usually, these issues pop up from changes in the build rules rather than dune itself. We are quite sensitive to performance regressions since they are felt very acutely by the JST people.
Hmm it actually looks like it is a little faster
I think the main difference is that dune 3.0 is actually reporting what it is doing where dune 2.9 wouldn't say anything.
So looks like my initial feeling is incorrect.
I did observe some job number bottlenecks however when rebuilding a project. I had dune build in watch mode and sometimes it would get stuck with one job. When I restarted the watch process it went back to multiple jobs.
This happens quite infrequently and I haven't yet been able to reliably reproduce it.
Here is an attempt at showing this behaviour
It is just showing what
dune build -w with cache disabled does, vs a fresh
Indeed zero builds and in general startup for dune is much improved for me in 3.0
Last updated: Feb 04 2023 at 01:03 UTC