Hello Mike,
On 13. Oct 2008, at 1:59, mfoss wrote:
> By 'renders slower' I mean that the response time for the model to
> move when you use the mouse to rotate it is longer and choppier.
So one is latency, the other is performance.
Wrt latency you can use 'latency 0' in your config{}, but this comes
at a performance cost, since the compositing operations can no longer
be pipelined with the rendering of your remote nodes.
> Before I try to do options 2 or 3, I think I should solve the
> problem that I am having with SSH first.
As said, the network traffic from Equalizer should not go through ssh.
The only ssh traffic should be stdout/stderr logging, which should be
nothing at runtime with a release build.
> The remote (rendering) nodes are each at about 13% CPU utilization
> in the SSH daemon. The local node is at about 15% utilization by
> SSH. I have a suspicion that I am somehow transferring the ply model
> file over the network rather than using the file on the disk at the
> remote nodes.
The ply model is indeed transferred over the network, but only during
initialization (see Programming Guide for details).
> The node where the image is displayed is sending about 160 Mb/s and
> receiving about 32 Mb/s.
That's probably the frame buffer data for compositing. Try making you
destination window smaller, the framerate should rise and the traffic
should drop accordingly.
HTH,
Stefan.
_______________________________________________
eq-dev mailing list
[email protected]
https://in-zueri.ch/cgi-bin/mailman/listinfo/eq-dev
http://www.equalizergraphics.com
