again please need help with network rendering

[abstrax]

sorry, the screenshot I made was just using localhost, which is much faster than LAN. In the office we have a 1 Gbit/s LAN set up and that's what I get:

In other words, I achieve about 100MByte/s and with very large packets up to 105MByte/s, which is as expected.

So, lksmada your connection seems to run with 1Gbit/s, otherwise it should be much faster. I'm no expert in those things, so I don't have a good list of instructions how to figure out, where the problem is, but Google probably knows more. On the other hand, 100MByte/s is not too bad, so I'm wondering if there is not something else going on. How does it behave in small scenes (i.e. less than 1 million triangles and only a few small textures)?

Mike, your stats indicate you are not running with the full 1Gbit/s, but it isn't that bad that it would explain the times you experience, so there is likely something else going on here. Could you test it with a small scene (i.e. less than 1 million triangles and only a few small textures)?

The next step would be to log, what's going on internally. I will make a separate post for this.

Again, could you two try out some simple scenes - maybe directly in the Standalone, to exclude the plugin as culprit? Thanks a lot.

[aoktar]

See the times of phases of a frame rendering. How much is actually dedicated to rendering, how much for data creation and updating the octane. See pure render time from onscreen info line in picture viewer.

[miohn]

Hi,

I already tested that.
But the Slave never starts to render even with a very small and simple scene.
(only raised image size and samples, so that the rendering takes longer)

And thats the weird thing!
Whatever the connection is slower or faster, with a 20MB Ram-Scene
the Slave should start after some seconds. But it did not. "Updating ...."

I also tested a stanalone scene. Established the network-connection.
After starting rendering status in standalone (in green) sais: activity: (empty)

I think, there is a connection, but no data gets send over the network, so
the Slave never starts rendering.

regards
Mike

[abstrax]

Ok, let's dig a little deeper. As a next step, we should log what's going on on the master and the slave.

For that you have to enable logging for the master, slave and daemon by copying

octane_log_flags.txt

(106 Bytes) Downloaded 1135 times

into the Standalone directory on the master and the slave computer. This file will enable logging for the Standalone as well as the slave into the file octane_log.txt.

Also copy

octane_daemon_log_flags.txt

(98 Bytes) Downloaded 949 times

into the Standalone directory on the slave computer. This file will enable logging for the daemon into the file octane_caemon_log.txt.

To make sure that logging really gets enabled (the flag files are only checked during startup), you have to close all Octane stuff. Then launch the daemon, the master, enable net rendering, enable the slave in the net render preferences and then open a simple scene and render it for let's say a few minutes. If the slave didn't render or just very slowly or got killed or crashed, you can close the master, stop the daemon and then either send me the created log files via PM or post them here. There should be 3 log files: octane_log.txt on the master, octane_log.txt on the slave and octane_daemon_log.txt on the slave.

Thanks a lot!

[miohn]

Hi Abstrax,

here are the log-files.
But master did not create any logfile.

octane_daemon_log.txt

(14.9 KiB) Downloaded 404 times

octane_log.txt

(20.11 KiB) Downloaded 397 times

regards
Mike

[miohn]

Hi Abtrax,

could you find out anything with the log-files?

regards
Mike

[abstrax]

Hi Abtrax,

could you find out anything with the log-files?

regards
Mike

Yes, I had a look at the slave logs and according to the slave log, it rendered fine. It took about 3.5 seconds to send over the scene and in the end it contributed 3008 samples/pixel until you probably closed the master. So the logs say all was ok. Did you experience anything weird?

The reason why there was no master log is probably because you have the Standalone installed in the programs folder and you would have to run the Standalone with administration rights (right mouse button -> "Run as Administrator") to allow it creating the log file in the program folder. As an alternative you could just copy the Octane directory out of the program folder and run it from there or you could just open the log window and save it manually to some file.

But in a nutshell: The logs say, everything worked as expected.

[miohn]

Hi Abstrax,

so its a problem with the plugin?

btw. with this stanalone test, can I see (without log file)
somewhere inside the master if the slave GPUs are rendering?

Do you still need the logfile from master?

regards
Mike

[miohn]

Hi Abtrax,

and now?


regards
Mike

[miohn]

Hi Abstrax,

strange - don't know why - but its working now!

Now when rendering , for the first time, I see this activity
in the Slave-Daemon-Bat.

On the Master there is still status "updating" and still I cannot see,
that there is something going on, but rendertime now is half the time
than without network-rendering.

So, god thanks, its working now!

Next I'll try again with a bigger scene and will report.

thanks
Mike