Fri, Mar 29, 10:36 AM CDT

Welcome to the Poser 11 / Poser Pro 11 OFFICIAL Technical Forum

Forum Moderators: nerd

Poser 11 / Poser Pro 11 OFFICIAL Technical F.A.Q (Last Updated: 2024 Mar 01 1:21 pm)

banner

Welcome to the Poser Forums! Need help with these versions, advice on upgrading? Etc...you've arrived at the right place!


Looking for Poser Tutorials? Find those HERE



Subject: Network rendering and remote RenderQueue CPU usage...


NikKelly ( ) posted Sat, 06 March 2021 at 12:21 PM · edited Thu, 14 March 2024 at 4:52 AM

Okay, after an epic battle with Win'10 Workgroups etc, I'm actually remote rendering a test-scene with six LaFemme figures on new Box. This task made my CAD-Tower's local render via twin graphics cards promptly 'fall over', totally blank...

I'm still on toe of 'learning curve', had a few hair-tearing moments before I realised that PPro_11.3 queue manager spends about five minutes doing 'admin stuff', sending files to remote Box, before that render begins...

But, Box's task manager shows render is only using ~8% of available CPU resources, so barely one (1) thread of the Ryzen7's 8-core = 16 available.

PoserPro_11 manual offers no clue to why this should be. Box' queue manager offers no obvious options...

Any ideas how the remote render app may conscript more of Box' dormant CPU power ?


NikKelly ( ) posted Sat, 06 March 2021 at 4:27 PM

Still, 4½ hours in, Box delivered...

test003_0030.jpg


NikKelly ( ) posted Sun, 07 March 2021 at 9:21 PM

https://www.renderosity.com/rr/mod/forumpro/?thread_id=2958942

I raised as wish-list item for P_12, but may be an obscure bug in PP_11.3.

Or, possibly, some quirk of Box' Win'10 Pro system that would need a 'security' flag cleared... D'uh.


NikKelly ( ) posted Mon, 08 March 2021 at 9:22 AM

Ha !! With Firefly set in Poser, network app correctly renders with multi-threads.

After doing 'admin stuff', app spun up to 100% CPU usage: FF render took fifteen (15) minutes !!

So, I've suggested that 11.3's 'single thread' remote render bug be sought in Superfly area...

test005FF_0030.jpg


NikKelly ( ) posted Mon, 08 March 2021 at 9:32 AM · edited Mon, 08 March 2021 at 9:34 AM

FWIW, QueueManager 11.3.740


NikKelly ( ) posted Mon, 08 March 2021 at 7:20 PM

Curiously, same 'single thread' issue now seems to apply to PP_11.3's 'local' CPU-only Superfly renders, yet Firefly recruits up to 100%...

Have we been afflicted by a recent Win'10 update ??


NikKelly ( ) posted Thu, 11 March 2021 at 1:40 PM

SOLVED ! SOLVED !! SOLVED !!! It's excessive Progressive Bucket size !!

I thought to experiment with local renders on a simple scene, one LaF + swimsuit.

Superfly Path Trace Tile went straight to 100 %. Yeah, okay, but I prefer 'Progressive'...

Superfly Progressive went straight to 100%, too. WTF ??

After some iteration, I realised Poser had 'fired up' with its 'progressive' 0_volume +64_buckets defaults, but I usually set 64+1024 to make best use of my twin graphics cards. Seems such do not 'play well' with CPU-only renders. Bucket size is the main multi-thread killer. Break-over point seems to be 128+128...

For CPU-only Superfly renders, I got ...

Volume 0 ____ 16 ____ 64 ___ 64 __ 128 __ 64 __ 64

Bucket 64 ____ 64 ____ 64 __ 128__ 128 __ 256 __ 1024

CPU % 100 __ 100 ___100 __ 100 __ 90+ __~75 __ 20%

And remote renders ? With 128+128 set, six-up scene is now rendering with 95~~100% CPU, ~10x faster. And done. Took 36 mins instead 5½ hours. By reducing the bucket size to 64, could probably shave five minutes...

So, not a bug as such, but a 'gotcha'.


NikKelly ( ) posted Tue, 20 April 2021 at 7:11 AM

May we have a designated corner of Rendo forums for network rendering issues & ideas ?

Being able to hang a modest, perhaps superseded PC on home network to do CPU-only renders without throttling main PC is so handy...


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.