I tried pyro simulation on my pc because I thought the reason is my pc. but when I tried pyro simulation, cpu usage was 100%. so there was no problem on my cpu. it would be a problem of PDG itself. but I don't know why
Edited by hamsteriscoming - Feb. 10, 2020 07:43:30
When the work is divided into a large number of jobs on your machine there is the potential for contention to cause overall slow down and glitching. It could be the GPU, CPU or I/O being over subscribed or hitting issues with video drivers etc. As you can see the batch case is very fast because there's minimal overhead. I would try reducing the number of jobs to see where the sweet spot it. You can do this by increasing the ‘Slots per Work Item’.
chrisgreb When the work is divided into a large number of jobs on your machine there is the potential for contention to cause overall slow down and glitching. It could be the GPU, CPU or I/O being over subscribed or hitting issues with video drivers etc. As you can see the batch case is very fast because there's minimal overhead. I would try reducing the number of jobs to see where the sweet spot it. You can do this by increasing the ‘Slots per Work Item’.
Thank you so much ! finally I understood! I tested many times and I figured out that same count of number of physical core and slot count makes best performance.