AWS Thinkbox Discussion Forums

Is there a CPU affinity limit

Hi all,

I was wondering if there is a CPU affinity limit with Deadline, when I try to select 128 threads per worker I get this error message.

rendernode:/var/lib/Thinkbox/Deadline10/slaves # /opt/Thinkbox/Deadline10/bin/deadlineworker -name "split-01-of-02" -nogui
WARNING: Ignoring HOME environment because effective user is root.
service was not added to the CommandLineParser.
Scanning for auto configuration
Auto Configuration: No auto configuration for Repository Path could be detected, using local configuration
Connecting to repository
Info Thread - Created.
Initializing WorkerStatusUpdate...
INFO: On Worker Started
Auto Configuration: Picking configuration based on: rendernode / ***.**.**.**
Auto Configuration: No auto configuration could be detected, using local configuration
Purging old logs and temp files
WARNING: Could not set affinity for the following CPUs because setting affinity on CPU 64 and higher is currently not supported: 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127

This is saying it’s not supported but I can find any information in the deadline docs. I’m also wondering if it isn’t supported now will it be supported in the future?

Thanks,
Ryan

Just found this post

Sounds like there was a work around. Was wondering if there is a workaround for Linux?

nope, not sure setting the CPU affinity in linux either, I gave up on this, letting concurrent tasks allocate cores is messy too

I’d posted here on my testing

I guess the affinity needs to be set outside of deadline, not sure if running the command under deadlineslave allows this?

Privacy | Site terms | Cookie preferences