From: Brendan S. <Br...@Br...> - 2007-04-22 13:09:25
|
Thanks Sam. I will take a look at Xming. One of the things I really like about VNC is that if I loose network connectivity, I can reconnect and not loose my session. X does not support this as it is session based (maybe things have changed?). This may not be an issue if using SLIRP or other fixed network addresses ? I did had this issue when using TAP and DHCP and getting different addresses when taking laptop to and from work. But I still don't understand why coLinux or VNC is sooooo slow. My understanding may be flawed? Here is my thinking: If I have a second PC running Linux and a VNC server, and connect from a MSW box using a VNC server over a 100Mbps network, I get much much better performance than if I use MSW/Colinux. I'd expect coLinux to get similar performance (or at least close). Assumption: given the two OSes are on the same machine I would expect network throughput would be better than two separate machines. However, I think the using the network support (particulary slirp) in coLinux is as slow, if not slower, than a real network Maybe because both host OS and guess OS are so resource intensive that the performance hit is extremely noticeable. If that is the case, then using any virtual OS would seem to useful only for playing and doing basic things. Thanks, Brendan. Sam Moffatt wrote: > First of all ditch TightVNC, you're not going to get decent > performance out of that and I'd suggest moving to an X server. Not > only will it improve network items, it will improve over all > performance. > > Xming is one I use that doesn't have too many issues. You can either > use XDMCP to connect in or use PuTTY with X forwarding. Again, you're > not going to get full native speeds from any GUI app as VNC has its > own repaint events (since it sends bitmaps) and Xming does a large > amount of context switches but network transfers are far more > efficient. > > Sam > > On 22/04/07, Brendan Simon <Br...@br...> wrote: >> I'm using coLinux and finding the GUI performance painfully slow. I'd >> like to find some ways to improve the performance, particularly as >> coLinux supposed to execute at "native" speeds. >> >> My configuration is as follows: >> >> * 0.8.0-devel-20070302 (2.6.17-co-0.8.0) >> * mem=512 >> * kernel=vmlinux >> * mem=512 >> * cofs0=c:\ >> * root=/dev/cobd0 >> * ro >> * eth0=slirp,00:D0:1f:99:88:99,tcp:22:22/tcp:5901:5901 >> >> * Debian Etch distro installed on a real ext3 hard disk partition >> (ie. not on windows file) >> * TightVNC with depth 24 and running a gnome session. >> >> * Laptop, Pentium M, 2GHz, 2GB RAM. >> >> >> Is there any way to speed things up? >> Is SLIRP just terribly slow? >> How much difference would changing the vnc depth to 16 or 8 make? I'd >> like to avoid that if possible :) >> >> Thanks, Brendan. >> >> >> >> >> >> >> >> ------------------------------------------------------------------------- >> >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> |