Fri Jun 20 18:40:01 2003
Having a problem with remote viewers watching one of my internal win2k boxes.
The win2k box has a screen resolution of 1280x1024x8 (just dropped screen
depth from 32->8). I have five people that watch the screen during the day
(business hours). On the screen is a graphics intensive program, so there are
lots of places (regions) that change and must be sent to the viewers.
I use TightVNC. I have nearly 1Mb/s of bandwidth into(out of) this building
and these people all have at least dsl or cable.
What it looks like to me is for sending a full screen 1280x1024x8=10485760
bits or 1310720 bytes or 1280k for a full screen refresh. The places where
screen is updated, if grouped into regions is 31 regions, and if left as
places of update it's probably three times that many. These updates happen
multiple times per second.
I'm thinking several things. For 1280k for the initial screen and then some
much?) per update, several times per second, to right now five remote
along a pipe that is almost 1Mb/s... I'm overloaded, right?
What things can be done to the existing system to speed things along and
reduce the lag for these remote viewers? I have reduced the screen depth.
I don't think I can use multicasting without modifying the code in some way.
Long-term I am writing a duplicate of the local application that can run
on the individual viewer's machines. I believe that solution will work until
get several hundered people (if ever) watching this application.