Cycles not using both NUMA Nodes on Dual Xeon Setup #61535
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#61535
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?
System Information
Operating system: Windows 7 pro 64bit
CPU: 2*Intel Xeon e5-2696v3
Blender Version
Broken: 2.80.xx
Worked: 2.79
Short description of error
When i render, Cycles wont use both NUMA Nodes (or CPU Groups) but only one. Even if i change from "Auto detect" to "Fixed" and fill in "72" inside the Performance-Tab, it spawns 72 Buckets but will actually use only 36 CPU Threads. While the auto detect option also didnt work in 2.79, the "fixed" parameter worked and used all 72 Threads for rendering.
Since this occurs only on this machine and not my second one (only 48 threads), my guess is that this is an issue with Windows CPU Grouping that will split everything that exceeds 64 Threads into Groups. If a software is not aware of this, they can only use one NUMA Node (or cpu Group). In my case that would be exactly 36 Threads.
Added subscriber: @Archimondro
#66549 was marked as duplicate of this issue
Added subscriber: @brecht
Which exact 2.79 and 2.80 version are you testing (date from the splash screen)?
Sorry,
Dosent work with: 2.80.44 (2019-02-07)
Works with : 2.79.6 (2018-11-09)
Added subscriber: @bazuka
Changed status from 'Open' to: 'Resolved'
Should be fixed by
8f1a558.Can confirm that it is working again on my dual e5-2696v3 machine. Autodetect will (as before) only show one node (36 threads in my case) but if i put in 72 manually, it uses all cores/threads. Thanks for fixing!