[Bf-cycles] Req: Access to new branch for distributed rendering using MPI and OpenMP (new Blender client not only for Cycles)

Jaros Milan milan.jaros at vsb.cz
Wed Jul 26 12:34:07 CEST 2017


Hi Sergey,

 

I forgot to mention there is some implementation of OpenMP for cloud ( <https://ompcloud.github.io/> https://ompcloud.github.io/). But In this case I mean only the base of OpenMP for shared memory ( = multi-threading, running on one PC), which contains GCC, MSVS or Intel compiler.

 

Best regards

Milan

 

 

 

Milan Jaroš 

Research Assistant

 

IT4Innovations national supercomputing center

VŠB – Technical University of Ostrava

17. listopadu 15/2172  |   708 33 Ostrava-Poruba   |   Czech Republic

 

e-mail:  <mailto:milan.jaros at vsb.cz> milan.jaros at vsb.cz  |   web: industry.it4i.cz   |    phone: +420 597 329 583   |    map:  <http://goo.gl/maps/BpF0z> goo.gl/maps/BpF0z

 

 

From: Jaros Milan 
Sent: Wednesday, July 26, 2017 12:28 PM
To: Discussion list to assist Cycles render engine developers <bf-cycles at blender.org>
Subject: RE: [Bf-cycles] Req: Access to new branch for distributed rendering using MPI and OpenMP (new Blender client not only for Cycles)

 

Hi Sergey,

 

There is big different between OpenMP and OpenMPI. OpenMP is for multi-threading application and it could be use on one PC with shared memory. OpenMPI is an implementation of MPI. MPI stands for “Message Passing Interface” and it is for using with distributed memory. It could be use for high-level network communication.

 

- How difficult it is to set up such an OpenMP farm ?

Installing and using of MPI it is very easy. For example on Ubuntu you can use standard package (sudo apt-get install openmpi-bin libopenmpi-dev)

 

- How much portable it is (Windows, OSX, Linux, BSD) ?

There is some implementation of this technology for different platform.

 

- What are the supported devices (my guess here is that there will be no GPU support, as in CUDA and OpenCL) ? 

MPI is for network communication (but more processes can work on one PC). The each blender client could use any other technology CUDA/OpenCL/OpenMP/OpenACC for communication with local devices.

 

- Why is OpenMP better for final render? I would assume that could cause quite huge networking overhead.

MPI could be use for small farm ( < 10) and big farm too ( > 1000 ). The using is much easier than sockets.

 

- Why do we need some distributed device support which is rather limited to what OpenMP is offering instead of improving existing device_network.cc (that oen would at least support all GPUs, will allow to do some data cache etc..) ?

Network devices use sockets and it does not support interactive rendering (we can add a switch for two technology MPI/Sockets into device_network.cc). The question is why we need for client/slave whole Blender? My suggestion is the using Blender client not only for rendering.

 

I hope it is better answer than Xeon Phi:)

 

Best regards

Milan

 

 

Milan Jaroš 

Research Assistant

 

IT4Innovations national supercomputing center

VŠB – Technical University of Ostrava

17. listopadu 15/2172  |   708 33 Ostrava-Poruba   |   Czech Republic

 

e-mail:  <mailto:milan.jaros at vsb.cz> milan.jaros at vsb.cz  |   web: industry.it4i.cz   |    phone: +420 597 329 583   |    map:  <http://goo.gl/maps/BpF0z> goo.gl/maps/BpF0z

 

 

From: bf-cycles-bounces at blender.org <mailto:bf-cycles-bounces at blender.org>  [mailto:bf-cycles-bounces at blender.org] On Behalf Of Sergey Sharybin
Sent: Sunday, July 23, 2017 3:55 PM
To: Discussion list to assist Cycles render engine developers <bf-cycles at blender.org <mailto:bf-cycles at blender.org> >
Subject: Re: [Bf-cycles] Req: Access to new branch for distributed rendering using MPI and OpenMP (new Blender client not only for Cycles)

 

Hi,

 

While i can see how this is benefitial for technical/farm usage, there are some concerns related on usefulness for Blender users:

 

- How difficult it is to set up such an OpenMP farm ?

- How much portable it is (Windows, OSX, Linux, BSD) ?

- What are the supported devices (my guess here is that there will be no GPU support, as in CUDA and OpenCL) ? 

 

There are also some technical questions:

 

- Why is OpenMP better for final render? I would assume that could cause quite huge networking overhead.

- Why do we need some distributed device support which is rather limited to what OpenMP is offering instead of improving existing device_network.cc (that oen would at least support all GPUs, will allow to do some data cache etc..) ?

 

Those are the main concerns of having this device exposed to Blender users. On another hand, if all the changes are living in device_openmp.cc and kernel/kernels/openmp with minimal code overlap, i done feel against having devices which are used by tehcnical guys and not exposed to Blender users.

 

That's y current questions and thoughts here anyway.

 

 

On Sun, Jul 23, 2017 at 3:07 PM, Jaros Milan <milan.jaros at vsb.cz <mailto:milan.jaros at vsb.cz> > wrote:

Hi, 

 

I would like to create a new Blender client not only for distributed rendering ( offline + interactive ).

 

I used my version of client for rendering some scenes of Agent327.

 

You can find more information here: http://blender.it4i.cz/research/distributed-rendering/

 

It could use OpenMPI or Intel MPI ( for using more PCs with Intel Xeon Phis/GPU ).

 

Best regards


Milan Jaroš
Research Assistant

IT4Innovations national supercomputing center
VŠB – Technical University of Ostrava

17. listopadu 15/2172  |   708 33 Ostrava-Poruba   |   Czech Republic

 

e-mail: milan.jaros at vsb.cz <mailto:milan.jaros at vsb.cz>   |   web: industry.it4i.cz <http://industry.it4i.cz>    |   phone: +420 <tel:+420%20597%20329%20583>  597 329 583   |    map: goo.gl/maps/BpF0z <http://goo.gl/maps/BpF0z> 


_______________________________________________
Bf-cycles mailing list
Bf-cycles at blender.org <mailto:Bf-cycles at blender.org> 
https://lists.blender.org/mailman/listinfo/bf-cycles





 

-- 

With best regards, Sergey Sharybin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-cycles/attachments/20170726/c60d449c/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4704 bytes
Desc: not available
Url : http://lists.blender.org/pipermail/bf-cycles/attachments/20170726/c60d449c/attachment.bin 


More information about the Bf-cycles mailing list