Johan Boekhoven

Johan Boekhoven

About Me



Recent Forum Posts

"While Loop", can we make TOP listen and act Aug. 1, 2020, 12:20 p.m.

As an addendum, it might be worth mentioning that any python operation that is calling file operations like process.Popen/ etc is best called in a python server and a Command Sent node. After many calls to it in a normal python node it locks up the UI and eventually stops processing all together. Not sure wby, but I think in the second run some thread/hooks are not cleaned up properly otherwise. I'm seeing this issue

PDG on TR3990X, NUMA nodes July 31, 2020, 4:29 a.m.

I put the scheduler on different settings, also 64 and more then 64, but it only ever burdens the first numa node. I also ran a second houdini instance with a simple flip sim (but very small particle separation). And that just ran over all 128 cores no problem. If you want me to test something just let me know. But so far I was unsuccessful to have PDG use everything.
Here's a screenshot of the numa node CPU burden, I have enough work items I think. But if you have a test file or something I'd be happy to run it.

PDG on TR3990X, NUMA nodes July 30, 2020, 9:34 a.m.

I'm running this on 18.0.532.

So it's PDG and COPs with ROP Composite outputs mainly and a small commandline utility at the end of processing to set some metadata in the JPG output.
We tried to turn of SMT and some other settings, but no performance gains, so we left it as default with 2 numa cores.