-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add module name to method show output (#19162)
* Add the method's module name to the show output * Update tests that involve showing a method
- Loading branch information
1 parent
9a46e9d
commit 7aba3f5
Showing
4 changed files
with
13 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7aba3f5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Executing the daily benchmark build, I will reply here when finished:
@nanosoldier
runbenchmarks(ALL, isdaily = true)
7aba3f5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @jrevels
7aba3f5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jrevels, there appears to be no imaginable way that this commit could have affected performance, so we seem to need to tune the statistics of the benchmarks again. It's frustrating that it's so hard to get performance measurements with reasonable accuracy.
7aba3f5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at the logs, it seems that past couple daily builds have been executing alternately on Nanosoldier's first and second worker nodes, which is the likely candidate for this variation. I can fix this by forcing daily builds to run on a specific machine, which should have been happening in the first place.
There's still the matter of normal builds being noticeably more noisy than they used to be for the past month or so (and those always run on consistent machines). The only change I can point to - besides Julia itself undergoing some changes, obviously - is that more benchmarks were added to the suite, increasing the total memory footprint of the benchmark suite. You also might notice that smaller groups of benchmarks (like
"linalg"
vs.ALL
) are less prone to noise.The above makes me inclined to believe my prior hunch that the spurious performance regressions are memory-related. I'd like to try having Nanosoldier load and run each module separately, as well as manually forcing a swap +
drop_caches
between them, to see if that cuts down on noise.@maleadt These kinds of fluctuations are a point in favor of your idea to use Codespeed to visualize the daily builds, if you're still interested in setting that up.