Marti_M
Nov. 8, 2019 09:31:47
Hi all.
I am struggling a bit with managing multithreading during the processing of the TOPs graph.
I have lots of light work that should run in parallel and the two steps that are memory intensive and need to run in sequence but on all cores.
Things I tried:
Creating new scheduler (set it to single only and the CPU or thread count to max) - this runs but never runs multithreaded.
Setting the FetchROPS to single only and the CPU or thread count to the max - this runs but never runs multithreaded.
Is there some magic to manage the CPU/count on a single work item? It always seems to be single-threaded.
Thank YOU!
BrookeA
Nov. 8, 2019 09:37:02
Hi, are you setting the Houdini Max Threads parameter in the Job Parms folder?
Marti_M
Nov. 8, 2019 09:43:43
Yes, I am. Any suggestions?
BrookeA
Nov. 8, 2019 09:47:03
Are you able to attach your .hip file?
Marti_M
Nov. 8, 2019 09:53:01
BrandonA
Are you able to attach your .hip file?
Indeed the scene is attached.
BrookeA
Nov. 8, 2019 10:57:10
Hmmm, I'm not able to reproduce the problem. I'm seeing max utilization across all of my cores when I run the ROP Fetch. A couple questions:
- Which Houdini build are you on?
- Which operating system are you using?
Marti_M
Nov. 8, 2019 11:01:48
- Which Houdini build are you on?
Latest production build. 17.5.425
-Which operating system are you using?
Win 10 currently
will try to nuke my preferences and see if it helps.
Marti_M
Nov. 8, 2019 11:08:57
Update resetting prefs helped.
Thank you for the help Brandon (kinda pointed me to it is me not you") direction! Now to figure out what was the culprit.
M
BrookeA
Nov. 8, 2019 11:15:34
No problem! When a job is scheduled by the local scheduler, it will set the job's HOUDINI_MAXTHREADS environment variable to the value of its Houdini Max Thread parameter. If something in your environment was overwriting that value, that may be a potential culprit.
Glad that it's working now!