Tweet
Issue:
When doing a DR animation-job, the initiating machine starts sending information to slave machines. The longer the job takes the more resends of informating occur. After a while the slave machines drop-out on the rendering job, with an "not responding" message.
We are using VIZ 2007 & VRAY 1.5 RC3 on 10 Windows XP Pro sp2 machines, and 3 Windows 2000 Pro workstation machines.
We are trying to find out what the issue is, causing the drop-out of the slave-machines.
Here is what we know:
There is a known issue with XP SP2, limititing the number of concurrent tcpip-connections to 10 per second, whereas earlier versions of the OS system were unlimited. (There is a different limitation for all NT platform machine which limits the number of connection to network shares to 10 for workstation editions.)
The 10 connections per second limition is know to be an issue for P2P programs as well, giving simular behaviour. Dropping out on network-connections, eventually resulting in network congestion.
I suspect we have a simular problem with the V-RAY spawner. In many P2P programs, developers started building in a timing the mechanism for the outgoing tcpip connections, to stay within the SP2 connection limits of 10 per second.
Does anyone know how VRAY operates in this manner???
When doing a DR animation-job, the initiating machine starts sending information to slave machines. The longer the job takes the more resends of informating occur. After a while the slave machines drop-out on the rendering job, with an "not responding" message.
We are using VIZ 2007 & VRAY 1.5 RC3 on 10 Windows XP Pro sp2 machines, and 3 Windows 2000 Pro workstation machines.
We are trying to find out what the issue is, causing the drop-out of the slave-machines.
Here is what we know:
There is a known issue with XP SP2, limititing the number of concurrent tcpip-connections to 10 per second, whereas earlier versions of the OS system were unlimited. (There is a different limitation for all NT platform machine which limits the number of connection to network shares to 10 for workstation editions.)
The 10 connections per second limition is know to be an issue for P2P programs as well, giving simular behaviour. Dropping out on network-connections, eventually resulting in network congestion.
I suspect we have a simular problem with the V-RAY spawner. In many P2P programs, developers started building in a timing the mechanism for the outgoing tcpip connections, to stay within the SP2 connection limits of 10 per second.
Does anyone know how VRAY operates in this manner???
Comment