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
Copy file name to clipboardExpand all lines: notes/performance.md
+1
Original file line number
Diff line number
Diff line change
@@ -3,3 +3,4 @@
3
3
* Ensure server GC is enabled.
4
4
* Bear in mind the later versions of dotnet core use tiered compilation, and this is enabled by default from dotnet core 3.0 onwards (see https://docs.microsoft.com/en-us/dotnet/core/run-time-config/compilation)
5
5
* Consider spectre/meltdown mitigations. This will hopefully be increasingly irrelevant over time; the initial mitigations had significant impact on some specific subroutines (but not sure about the overall effect on SharpNEAT).
6
+
* I noticed a significant performance drop on the v4.1 code base between its release in December 2023, and Jan 2025. I think this must be caused by Windows 11 updates as I eliminated dotnet9 as a possible cause; as such I think it would make sense to run efficacy sampling runs on Linux from now on.
0 commit comments