[Cin] Rendering multi-threads

[Phyllis Smith]

Andrea,

If I decide to use 14 jobs in the renderfarm, starting from node 1025,
> I have to open 14 terminals and in each of them write:
> {path}./cin -d (or -D?) 1025
> then 1026
> ...
> 1038
>

No, you just need to use 1 terminal window and keyin:
  {path}./cin -d 1025
  {path}./cin -d 1026
  {path}./cin -d 1027
  {path}./cin -d 1028  and so on (I could not get uppercase D to work)

Here is an example of what I did and saw:

# ./cin -d 410
Cinelerra Infinity - built: Jun 25 2020 19:59:25
git://git.cinelerra-gg.org/goodguy/cinelerra.git
(c) 2006-2019 Heroine Virtual Ltd. by Adam Williams
2007-2020 mods for Cinelerra-GG by W.P.Morrow aka goodguy
Cinelerra is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it under
certain conditions. There is absolutely no warranty for Cinelerra.

# RenderFarmClient::main_loop: client started

Then when you keyin the next line, you will see these jobs sitting around
waiting for something to do:
# ps -ef | grep cin
root        3621    3342 99 15:45 pts/1    02:39:35 ./cin
root        4658    1272  0 16:05 pts/2    00:00:00 ./cin -d 401
root        4662    1272  0 16:05 pts/2    00:00:00 ./cin -d 402
root        4666    1272  0 16:05 pts/2    00:00:00 ./cin -d 403
root        4670    1272  0 16:05 pts/2    00:00:00 ./cin -d 404
root        4674    1272  0 16:05 pts/2    00:00:00 ./cin -d 405
root        4678    1272  0 16:05 pts/2    00:00:00 ./cin -d 406
root        4686    1272  0 16:05 pts/2    00:00:00 ./cin -d 407
root        4690    1272  0 16:06 pts/2    00:00:00 ./cin -d 408
root        4694    1272  0 16:06 pts/2    00:00:00 ./cin -d 409
root        4698    1272  0 16:06 pts/2    00:00:00 ./cin -d 411
root        4704    1272  0 16:06 pts/2    00:00:00 ./cin -d 412
root        4708    1272  0 16:06 pts/2    00:00:00 ./cin -d 413
root        4713    1272  0 16:06 pts/2    00:00:00 ./cin -d 414
root        4717    1272  0 16:06 pts/2    00:00:00 ./cin -d 415
root        4721    1272  0 16:06 pts/2    00:00:00 ./cin -d 416
root        4733    1272  4 16:07 pts/2    00:00:00 ./cin -d 410

THEN you start the render and if you watch with the command line "top", you
will see the 15 jobs all running and if you look in the directory where you
rendered the file to, you will see 15 files changing size.  When each of
the cin -d jobs finish, you will see in the terminal window where you
started them, the following:
   RenderFarmClientThread::run: Session finished.
   RenderFarmClientThread::run: Session finished.
   RenderFarmClientThread::run: Session finished.
   RenderFarmClientThread::run: Session finished.    and so on


- "cin" gives me "unknown command" error, "./cin" works instead.
>
I will fix the manual to correct "cin" to be "./cin" instead.

>

> - RenderMux does nothing; I certainly don't know how to use it.
>
RenderMux will not do anything until the render farm rendering is
finished.  It is just used to put the 15 files together.  GG puts the files
together all of the time and sees no weirdness between the files.  You have
to use RenderMux in the same session that you rendered right afterwards
because it keeps track of the file name you chose (or you can run it
manually later from {path}/doc/RenderMux.sh  )

However, on my laptop with 16 cores, BigBuckBunny 1920x1080 rendered using
all 11-14 cpus automatically and took almost 10 minutes.  When I used the
Render Farm method instead, it took 9 minutes so IT IS MORE IMPORTANT TO
FIGURE OUT WHY YOUR COMPUTER IS NOT USING MULTIPLE THREADS TO RENDER.

> --
> Cin mailing list
> Cin at lists.cinelerra-gg.org
> https://lists.cinelerra-gg.org/mailman/listinfo/cin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20200626/d0aa699a/attachment.htm>