Version 0.9.5.0 #66
sp00n
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This version is a somewhat bigger overhaul:
runtimePerCore
setting for y-Cruncher as well. It will test all selected cores for one core and then proceed to the next one(this is made possible by a custom wrapper .exe and .dll in the /helpers directory)
restartTestProgramForEachCore
is selected.Note that running with two threads and without the setting enabled may result in very long test times on the E-Cores and any test afterwards, so it's strongly recommended to either enable
restartTestProgramForEachCore
, test only with one thread, or test the P- and E-Cores separately.testDuration
setting for y-Cruncher that allows to set the test duration in seconds for each individual test (default: 60)It's not treated as a "real" error, as it doesn't necessarily coincide with the core that is currently being tested.
You can disable this check with the
lookForWheaErrors
setting.To be able to use this functionality, the script asks the user if a new "Event Source" should be added, which requires administrator privileges. This only needs to happen once, so after this "Source" has been added, no administrator privileges will be needed anymore. The script itself also doesn't need admin rights, instead it will open a new window to perform this action, and asks for elevation for this new window.
The Event Log entries can be found in the "Windows Logs"/"Applications" section of the Event Viewer, and have the source "CoreCycler".
This functionality can be controlled by the
useWindowsEventLog
setting in the[Logging]
section.flushDiskWriteCache
in the[Logging]
section)If you really want to, you can re-enable the use of the Windows Performance Counters by setting
useWindowsPerformanceCountersForCpuUtilization
in the[Debug]
section, but I really advise against it.beepOnError
setting)flashOnError
setting)This is required to be able to set the affinity for more than 64 CPUs, and also to fix a bug that appeared on Intel systems, where if set to use two threads, the two virtual CPUs weren't fully loaded if only the main program's affinity was set.
You won't be able to easily see the current affinity using the Task Manager anymore, but a tool like System Informer can also show the current affinity for threads
00-x86
algorithm anymore, so the new default low-load binary algorithm is04-P4P
insteadstressTestProgram
toYCRUNCHER_OLD
Be aware that you will also need to adjust the
tests
setting in the config if you're switching between the versions!Set-StrictMode -Version 3.0
setting. This may introduce new and fun script error messages, but hopefully I have already caught most of them!This discussion was created from the release Version 0.9.5.0.
Beta Was this translation helpful? Give feedback.
All reactions