Forum Replies Created
-
sort them for username
There’s a specific reason for this feature design.
Even you think it transfers a couple of bytes, remember that a TCP packet is always 512 bytes of size.
Apart from that, Muster uses a FIFO network protocol using TCP, that means that every packet is put into a queue waiting for network delivering. Scheduling an automatic message every X seconds may lead to an internal buffer overflow under heavy network usage, even using an intelligent substutable message queue.
Now, thinking at a 200-300 host farm, having those messages in queue isn’t a real problem, but the delay it may cause to most important messages (completation of renders) may lead to lost of precious seconds.
Don’t think in a “gigabit” way. When under usage, there’s a good chance that your network is in a “full” status at about 80% of the rendering times due to file streaming. The only way to make that really working in the way you’re describing is the define of a local policy of QoS (Quality of service) directly on your switches (that must be layer 3). Unfortunately, this is something that’s done by a very low level of end users.
Just to close the case, we’ll make that feature user-configurable in the near future.
Cheers
