You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently this is done manually by building Chromium before and after a commit. I think it would be good to have a script, which you can pass two commit hashes and a path to a Chromium source, which will then compare the -d stats result.
Would it be useful to have smaller but also ubiquitous packages? Maybe in Fortran too, like Lapack that is a couple thousand files mostly in Fortran.
Typically for benchmarking one tries to do several repeated runs to mitigate unpredictable externally-driven slowdowns.
Maybe look to the packages Phoronix frequently uses for build benchmarking?
Currently this is done manually by building Chromium before and after a commit. I think it would be good to have a script, which you can pass two commit hashes and a path to a Chromium source, which will then compare the
-d stats
result.Maybe add the functionality to
misc/measure.py
?See #1577 (comment)
The text was updated successfully, but these errors were encountered: