2010/5/19 Saket Jalan <saaketjalan@gmail.com>
> hello
>
> I am new to VNC and its protocol and want to know how do we benchmark VNC
> and on what basis (it's bottleneck)?
>
VNC has various bottlenecks. SInce it is used in communication every step in
the process is a potential bottleneck. As with every bottle, necks come in
sizes.
In the beginning, the system administrator is the bottleneck, as he/she
needs to install the stuff. As long that is not happened, it is the cap on
the neck of the botlle, or the cork in the bottleneck.
The VNC steps from remote to local include:
- the display hardware on the remote side (used in msWindows remote
implementations)
- the conviguration at hte remote side (if the display is huge wiht high
color depth, it takes a lot of data to process)
- the cpu power at the remote side: see above
- the network connection between remote and local. Including tunneling,
compression, encryption and the lot. VNC is known to work (I have
experience) over a 33K-baud (33000 bits per second) phone line, even
relative workable...
- the local side, using the binary or java implementation, native on the
display, using a window manager or what ever.
In the end, I'd say the user is the bottleneck as they cannot type faster,
mouse more or view larger pictures.
For what its woth, vnc has various usages. Pick your usage, put it on your
system and if it does not work fast enough, investigate which steps are on
the route and measure which one is your bottleneck.
If you are stuck, carefully describe your environment and come back to us.
> Please help!!
>
> --
> Regards
> Saket Jalan
> _______________________________________________
> VNC-List mailing list
> VNC-List@realvnc.com
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
>
_______________________________________________
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list