Page MenuHome

Setting Thread Count
Closed, ResolvedPublic

Description

System Information
Operating system: Windows 10 pro
Graphics card: GTX 1060 gigabyte

Version: 2.80 Date:2019-01-01 20:52 Hash: 4b7596ec914e

Crash upon rendering an image after changing the thread count from Auto-Detect to fixed (from 16 to 18 threads)

Open a new scene, change rendering engine to cycles, change thread-count to fixed instead of Auto-Detect, 1ncrese value to anything greater than 16, hit f12 or render the image, hard crash.

Event Timeline

Sergey Sharybin (sergey) triaged this task as Confirmed priority.Sun, Jan 6, 12:14 PM
Sergey Sharybin (sergey) claimed this task.

Will only happen when setting number of threads to something higher than the physical number of processor threads.

@Brecht Van Lommel (brecht), i'm a bit on a split here. Shall we support this (and allow more than one Cycles thread on a CPU thread), or we'd better clamp number of threads in a pool? I kind of see benefits in both approaches.

Sergey Sharybin (sergey) raised the priority of this task from Confirmed to Unbreak Now!.Sun, Jan 6, 12:14 PM

I think we can continue to allow a higher number of threads, but just not set any affinity for them (assuming that's the issue)?

@Brecht Van Lommel (brecht), well, we need to set some affinity, to "decouple" it from the main thread (which is using node 0). Not a big deal to implement, was more wondering what is the best thing to do.

Will get it fixed after solving render issues for the studio.