I'm not sure what you mean by "VNC configuration".  If you are referring to
the various polling options, then I can say that a 2CPU (4 virtual
processors) 2GHz Xeon box has worse performance than a Celeron 566 with
identical settings, over the same network.

Since this seems odd to me (that a far faster box has far worse
performance), I had been attributing it to the number of CPUs (our dual-CPU
boxes also have worse performance than a uniprocessor machine, all else
being equal).

If there are any registry tweaks I can do to get better performance, please
let me know.  I'd also be interested in a way to lock the winvnc service to
a single processor (in the hopes that this would alleviate some/all of the
slowness).

Unfortunately, it seems (from the complete lack of response from
listmembers) that most people don't use VNC on dual-CPU boxes.  Can anyone
confirm or deny this slowdown?  It's pretty noticable, so if you are using
dual or 4way boxes with VNC, you'd be hard pressed to not realize that it
was slower.

I'd just like to find out if the slowdown I'm seeing is generally
experienced, or if there is something I can tweak to fix it.

Thanks,
Jordan

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of Dr. James Wez Weatherall
> Sent: Thursday, March 06, 2003 3:02 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: VNC 3.3.7 released
>
>
> Jordan,
>
>       There may be some performance improvement between 3.3.6 and
> 3.3.7, but
> it depends heavily upon your VNC configuration.
>       Cheers,
>
> --
> Dr. Wez @ RealVNC Ltd. - http://www.realvnc.com
> Open Source VNC - Commercial Support & Development
>
> ---
> Does anyone know if:
> "Improved reliability of Windows VNC server on multi-processor systems."
>
> means that the performance doesn't suck on multi-processor systems
> anymore?
> I'd not had problems with the service crashing on me (which
> "reliability"
> connotes, to me anyway), but it is /dog/ slow.
>
> I've installed it on our system, but, alas, it requires a reboot to
> start it
> up again, and it's a production machine, so I can't take it down.
> ---
> _______________________________________________
> VNC-List mailing list
> [EMAIL PROTECTED]
> http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to