|
|
On 8/2/2022 2:39 AM, Scott wrote:
>>> The solution is to keep priority as "Normal" in POV, then immediately after
>>> starting the render, go into Task Manager and change the priority of the POV
>>> process to Normal. This then makes it use all logical cores.
>>>
>>> A bit inconvenient, I wonder why "Normal" in POV is converted to "Below Normal"
>>> in task manager?
>>>
>>>
>>>
>> Use the high priority with +wt22. That'll leave two cores for other
>> tasks. Or, use +wt23, leaving 1 core for the OS and other processes. You
>> may want to add that switch directly in quickres.ini
>
> Good idea, I found I need to go down to +wt20 to keep the OS properly responsive
> (+wt22 is still very slow for opening apps etc). Going down from +wt24 to +wt20
> increases render times on an example from 67 to 74 seconds, which is fine for
> short test renders.
>
>
Wouldn't a better fix, over the long run, be to have POV ask how many
cores there are, then determine how to set both how many it uses, and
what to tell the OS, based on that? Or, just have an option to have it
tell you how many are available, and adjust how many you let it use, in
the application? Having to mess with the number of cores (especially if
you have no clue), or monkey with what the OS is looking at, after its
starts a render, seems.. unnecessarily fiddly.
--
Commander Vimes: "You take a bunch of people who don't seem any
different from you and me, but when you add them all together you get
this sort of huge raving maniac with national borders and an anthem."
Post a reply to this message
|
|