Fri, Nov 29, 10:07 AM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Nov 26 6:57 am)



Subject: Vue -Networkrendering and Cores


copter ( ) posted Mon, 18 March 2013 at 8:00 AM · edited Wed, 27 November 2024 at 5:52 PM

Hi!

I have a server with 48 x 2.2Ghz cores with RenderCow 10.5 installed. The problem is that when i send it a job it only renders one tile at a time (using only 1 core).

I have tried to find a solution but the only answer i can find is to reinstall RenderCow, which did not work. If anyone have any idea about how to fix this it would be lovely!


ShawnDriscoll ( ) posted Mon, 18 March 2013 at 11:10 AM · edited Mon, 18 March 2013 at 11:11 AM

When you connected your main system to a node for the first time that had rendercow installed, do you remember your main system pushing the latest rendercow build to the node?

www.youtube.com/user/ShawnDriscollCG


copter ( ) posted Mon, 18 March 2013 at 12:12 PM · edited Mon, 18 March 2013 at 12:13 PM

Did not get any info about something like that.

At the moment the setup looks like this

Main comp(win_7-64bit) with Vue Xstream and Hypervue.

Server with (Win_server2012-64bit) with RenderCow.

The server shows up in HyperVue but only renders with a max load of about 10%, and only renders 1 tile at a time. Does not matter if i force tile sizes.

 

edit: and im not using the plugins, only standalone xStream.


ShawnDriscoll ( ) posted Mon, 18 March 2013 at 12:28 PM · edited Mon, 18 March 2013 at 12:33 PM

Ok.  Sounds like you may have installed the node using the same build as your main system is using.

So something has to tell the node how many cores it's running on.  Or maybe each node gets one system to run on, and that system uses multi cores for that one bucket.  It's been awhile since I used nodes.

When you render locally on your main system, do you get multiple buckets?  Can you see multiple cores working on a render?

However your main computer behaves with Vue, the node should behave the same way.

Are renders finishing sooner using the node?

I reread and saw the 1 core being used.  Check with e-on to see if there is a ZIP file that was a patched rendercow installer for 10.5.

Double-check that the rendercow build is the same as your current Vue build.

www.youtube.com/user/ShawnDriscollCG


bruno021 ( ) posted Mon, 18 March 2013 at 12:36 PM · edited Mon, 18 March 2013 at 12:37 PM

1 machine = 1 cow, not 1 core = 1 cow. Doesn't matter how many core you have on one machine, one machine is one cow. 1 machine renders one tile at a time, but should use 100% power, not 10.



copter ( ) posted Tue, 19 March 2013 at 5:19 AM

All the builds are the same version. My main comp is using 100% load on all 8 cores. The render is slower while using the server. If i check the CPU Affinity on the rendercow installed on the server it reads 48, which is the correct number of cores.

@bruno, so the tilesize is the amount of "pixels" that get sent to the nodes and then the nodes themself split them into parts that get distributed among the cores?


copter ( ) posted Tue, 19 March 2013 at 5:23 AM

Vue Xstream 10.5 build 10501461 on main comp.

Rendercow 10.5 Infinite build 10501461 on both the main comp and the server


bruno021 ( ) posted Tue, 19 March 2013 at 9:22 AM

Tile size is indeed the size of a single "chunck" that each cow will render



ShawnDriscoll ( ) posted Tue, 09 April 2013 at 11:49 AM

I have a new computer with 8 cores.  Some scenes have all cores rendering the same bucket.  Other scenes I have all cores rendering their own bucket.  It must be a load balance thing that Vue does.  I just assumed Vue would assign a core to each bucket reguardless of how long it might take.  Maybe Vue does that, actually.  It keeps assigning cores to the same bucket until that bucket is rendered.

www.youtube.com/user/ShawnDriscollCG


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.