Hey Ono-Sendai...
Now after adding multithreading to Indigo your Renderer runs like hell
But by using both of my Cores the System just respons slower,
because Indigo uses all my CPU Power,
so I always have to reduce Process Priority to a lower Level by hand...
Is it posible to add Process Priority definition to the inifile.txt,
so I (and everybody else ) don't always have to change it by hand,
if I want to keep working on my PC?
I think this is a loooooow Level Request, kind of luxus, but still handy
bye, and thanx for your great Render!!!
Request: Process Priority
Re: Request: Process Priority
Hello ,Zom-B wrote:Hey Ono-Sendai...
Is it posible to add Process Priority definition to the inifile.txt,
so I (and everybody else ) don't always have to change it by hand,
if I want to keep working on my PC?
I think this is a loooooow Level Request, kind of luxus, but still handy
psExec (sysinternals.org) can launch a process with a given priority (haven't tried it though)
Hmm... isn't a good Idea you say... may I ask why???radiance wrote:i would'nt integrate this into the indigo core as it's not a good idea to let processes govern they're own priorities.
it's also not very portable from a coding point of view...
By portable you mean, you can use the same exe on linux/unix
that I use on my Win PC???
Yes it doesOno-Sendai wrote:I'll test out the priority stuff sometime and see if it helps.
Using all cores / virtual cores at once does totally own a computer eh
The luxus of smoth multitasking on dual Core is gone, fells like my old 1 Core PC ^^
Using 3 threads more than using just using 2, but I stilll got other Stuff running...
Has anyone run some testing on 0.6 to see if multiple threads is faster than multiple clients (networked)? Just thinking, if you're needing to "break in" to the rendering process periodically to gain access to some CPU time for other stuff, then the client system is great for this. Just kill one of the clients when you need the power and fire it back up when you're ready to crunch in Indigo. But, if threads are faster, then... priorities can be changed on the fly in the TM.
Alternately, and I know this has been requested before, but if a render could be completely stopped, then resumed at a later time... that'd be cool! A big use of this might be for animations. You have a set number of frame files, say 300, and you render thru all @ 20 min each. Then you can cycle thru them again, refining them for another 20 - and soforth until you get to acceptable quality levels. Combining this with anti-noise filters might make animation possible!
Alternately, and I know this has been requested before, but if a render could be completely stopped, then resumed at a later time... that'd be cool! A big use of this might be for animations. You have a set number of frame files, say 300, and you render thru all @ 20 min each. Then you can cycle thru them again, refining them for another 20 - and soforth until you get to acceptable quality levels. Combining this with anti-noise filters might make animation possible!
-mzungu
"The fear of the Lord is the beginning of wisdom" - Solomon
"The fear of the Lord is the beginning of wisdom" - Solomon
Who is online
Users browsing this forum: No registered users and 101 guests