Flame graph files get increasingly large with Function entries, which not only have long names but there are a lot of them.
We could argue functions that take a low amount of time to compile are adding noise instead of helping you detect issues in your build times.
It would be interesting discarding those functions that take less than a number of some time unit (i.e. those that take less than 10 milliseconds?).
We could add an optional command-line option for this number and use a default value if missing.
Flame graph files get increasingly large with
Functionentries, which not only have long names but there are a lot of them.We could argue functions that take a low amount of time to compile are adding noise instead of helping you detect issues in your build times.
It would be interesting discarding those functions that take less than a number of some time unit (i.e. those that take less than 10 milliseconds?). We could add an optional command-line option for this number and use a default value if missing.