Blender Benchmark - multi socket CPU setup does not allow to run the benchmark #56443
Labels
No Label
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Information from Developers
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Design
Type::Report
Type::To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/blender-open-data#56443
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi, Martin here from GarageFarm.NET.
I have tried your new benchmark utility and noticed an issue that the benchmark won't run on a multi socket setup.
We have nodes with E5-4669v4 CPUs which can be run in 3 configurations: 1CPU, 2CPU, 4CPU. I can run the benchmark without issues on 1CPU setup, but not on 2CPU or 4CPU.
I launched Blender Benchmark from command line and here's the error log:
It is a problem with reading the number of cores. I was able to launch the benchmark after editing file system_info.py and setting fixed number of cores in that line (22 in our case).
Added subscriber: @GarageFarm.NET
#56480 was marked as duplicate of this issue
Added subscribers: @beCoarse, @dr.sybren, @brecht
Added subscriber: @RomanGischig
if changed in the script manually to the right value, all works fine:
file: system_info.py
system_info['cpu_brand'] = cpu_info['brand']
Added subscriber: @SemMulder
Changed status from 'Needs Triage' to: 'Resolved'
This should be fixed with the new version of the launcher available at https://opendata.blender.org/. Closing for now, feel free to reopen if problem persists.