Menu
▾
▴
Re: [coLinux-devel] RE: Problem running KDE
|
From: <my...@gm...> - 2004-02-18 18:59:20
|
I actually have been running KDE remotely for over a year with no
problems. At work, I have a 1GHz Windows 2K PC with Cygwin/X11 server
connecting to a 1 GHz Linux PC over the corporate LAN (100Mbps with a fair
amount of network traffic). It is actually faster to run KDE remotely on
Linux than running it localy on Cygwin! I turned off the KDE animation
effects and sound and it words great. Although KDE is more heavyweight
that the original X apps, most modern PCs and LANs have much more capacity
than what was available in the early days of X. I would expect that KDE on
cL should be able to just work fine over a loopback connection - its just
a matter of working out all of the issues.
Larry
> I think that one of the problems is that KDE and Gnome are not designed to
> be run over a network connection. They are just too heavy to do that now
> unless you have a seriously fast network pipe. Their targets are desktop
> machines after all. I think the symptoms could be that services are
> silently timing out as the code is not intended to be run in this way
> (though fot example the dialog for arts daemon timing out etc is a recent
> implementation in kde).
>
> Historically window managers were mostly run over network connections from
> X-Terminals and there are many others to choose from: fvwm2 and
> Enlightenment do the job. If the virtual network card ran at a higher
> throughput (I have not done any benchmarks so I dont know what it is)
> things may be better. Being realistic Cygwin/X is pretty slow anyway.
> Having thought about it I would not expect running X apps remotely from it
> to be faster as they could only be slower because of the network link. How
> about conecting a physical machine and getting a baseline? All in all I
> consider this capability provided by coLinux to be a proof of concept.
>
> Something that I am currently looking at is tweaking KDE and/or Gnome so
> that all of the eye candy is disabled etc to alleviate some load. Perhaps
> try disabling sound before the session is started as sound wont work
> anyway and this is one of the things that I find on a native Linux box
> impairs performance. There are also patches to the kernel that optimize
> the scheduler and so on. Perhaps these could be applied. No idea. 2.6? I
> think that I will end up waiting until a virtual graphics card is
> implemented in coLinux as in vmware (the diffs for their card are
> available for this from their site btw as it is open source).
>
> Anyone had any other ideas along this line?
> ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÒó^¶+,¦ì¢·o/Ò¥çJÖ«µ.¬¸§»)¦ÃhÃðnWZ×^¦Z2jlýg±êïǬ~Ë{±Â+aiúÞx5C²íÁªÞ+_®ÏÂ'$6ÿÛiÿÿÚvÏè±Ùÿr¿ý§ÿßÿjYhsøóú)rOÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿýÊ {±ýׯzYX§X¬µÊ {±ýׯz_åËlþÊ.Ç¢¸ þwÛi³ÿÿ+-³û(º· ~à{ùÞ·ùb²Û?+-wèýÊ%{±ýׯ
>
|
