Multi-threading: Single work Item

   3035   8   0
User Avatar
Member
11 posts
Joined: 9月 2015
Offline
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!
Edited by Marti_M - 2019年11月8日 09:33:27
User Avatar
スタッフ
387 posts
Joined: 8月 2017
Offline
Hi, are you setting the Houdini Max Threads parameter in the Job Parms folder?
User Avatar
Member
11 posts
Joined: 9月 2015
Offline
Yes, I am. Any suggestions?
Edited by Marti_M - 2019年11月8日 09:46:26

Attachments:
Scheduler.jpg (91.9 KB)

User Avatar
スタッフ
387 posts
Joined: 8月 2017
Offline
Are you able to attach your .hip file?
User Avatar
Member
11 posts
Joined: 9月 2015
Offline
BrandonA
Are you able to attach your .hip file?
Indeed the scene is attached.

Attachments:
ISLAND.hiplc (1.8 MB)

User Avatar
スタッフ
387 posts
Joined: 8月 2017
Offline
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?
User Avatar
Member
11 posts
Joined: 9月 2015
Offline
- 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.
Edited by Marti_M - 2019年11月8日 11:02:32
User Avatar
Member
11 posts
Joined: 9月 2015
Offline
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
Edited by Marti_M - 2019年11月8日 11:11:33
User Avatar
スタッフ
387 posts
Joined: 8月 2017
Offline
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!
  • Quick Links