Forum Comments

My tests
In General Questions
sr.loire
Mar 07, 2018
Really happy to help! Here are more tests: Crowdrender version 0.13 release (updated from pre-release) Single frame render. f12 means rendered only in the main machine. cr means rendered with the Crowdrender button. When rendered in CR i've made several renders in a row to take into account the balance calculations. Render time in seconds. From the previous test I updated Blender to 2.79a and CR on every machine. With 0.13 final the second slave machine connects! Still have to start blender in terminal, no luck connecting to blender UI with the add-on in the Manjaro Linux machines. So the setup is: Main machine: CPU Intel core i5-4460, 3.20GHz 4 cores (no hyper threading) RAM 8GB DDR3 GPU Nvidia Quadro K620, 384 CUDA cores, Driver 376.33 Windows 7 Blender 2.79a (normally started with the GUI) with CR add-on And Blender 2.79 daily for some tests Slave machine (x2): CPU Intel Core 2 6400, 2.13GHz 2 cores (no hyper threading) RAM 2GB DDR3, 8GB swap on a disk HDD GPU GForce 7300 GT and GPU GForce 7300 GTX (one on each machine) (no CUDA compatible, not used for rendering) Manjaro Linux 7.1.4 (last version rolling release) Blender 2.79a with CR in the terminal as instructed in this post: https://www.crowd-render.com/forum-1/general-questions/crowdrender-headless-comand-on-slave-computers Internal scene from my job (with denoiser): F12 - 3:06:06 CR - 4:57:74 - 5:01:29 - 4:45:75 - 4:53:03 - 4:01:54 - 3:34:86 - 3:19:93 -> Blender 2.79 daily-build with GPU+CPU (Only on the main machine, Slaves still with 2.79a): F12 - 2:17:95 BMW test scene, with 100 samples, didn't touch anything else (note that there's some CR balance calculated from the start from the previous renders... Is there?): F12 - 5:26:32 CR - 4:55:02 - 4:40:62 - 4:08:47 - 4:02:05 -> Blender 2.79 daily-build with GPU+CPU (Only on the main machine, Slaves still with 2.79a): F12 - 2:55:28 CR - 3:15:49 - 4:56:33 - 6:23:74 - 9:07:68 Some concluisons: My main computer benefits on most scenes from using the GPU+CPU feature. When using the daily build with this feature CR doesn't manage to improve render times and after each render unbalances the node setup increasing render times further. It did improve render times for the BMW scene in stable blender 2.79a, good for CR!, but it's still faster for me to use Blender daily with the GPU+CPU feature without CR. It seems that CR has some trouble before finally calculating a good balance between my nodes, it' would be great to set the balance manually for some cases like mine. Knowing my machines I would start setting a 80/10/10 work distribution. When i get some spare time I will test the main machine with my personal laptop wich has a close performance to the main one at my job.
0
0
s

sr.loire

More actions