From: Henry N. <Henry.Ne@Arcor.de> - 2007-12-21 19:46:50
|
Rainer Zocholl wrote: > pa...@wa...(Paul Waldo) 21.12.07 08:52 >> I am running the latest colinux (0.7.1), > > Please try the devlopement release 0.8. > It's stable enough for a developer ,) One interesting change exist for machines with DEP/noexecute and PAE (Physical Adress Extension enabled): In 0.7.1 colinux does "flush tlb" on every OS switch as workarrount to fix crashing Intel CPUs. coLinux version 0.7.2 and 0.8.0 runs the "flush tlb" only ones on startup. This can make CPU faster. The CPU cache is not cleared on every OS switch. Give the 0.7.1 from http://www.colinux.org/snapshots/ a try. It's a release candidate. ;-) >> and it seems to be running quite slow. >> The KDE UI is somewhat jerky because of the slowness, but >> my main concern is raw processing power. I am hoping to be able to do >> Java software development at work without having to interact with >> Windows. I'm willing to deal with the fact that coLinux is only using >> one of the two CPUs, but I can't justify using it on a daily basis if >> it takes significantly longer to do my job. CoLinux kernel runs only on the first CPU. That you can not change. The daemons and your Xserver should (can) use the other CPU. >> Here are the platform details: > >> Host >> ******* >> Windows XP >> coLinux 0.7.1 >> Pentuim D, ~3 GHz >> 3GB RAM > >> Guest >> ********* >> Kubuntu Gutsy i386 > >> I booted my Kubuntu Live CD and found that it reported the bogoMIPS at >> 5990.33. coLinux reports the bogoMIPS at 1520.43. That means the >> coLinux guest is running at ~25% of native speed. I know that >> bogoMIPS are not an true speed representation, but I think it is close >> enough to give a general idea of what is going on. bogoMIPS have no real timebase under coLinux. That means, you can not compair it with native boot. The function inside bogoMIPS calcuation is an OS switch under coLinux and a loop in native linux. If you feel, coLinux is slow, check the network you used. Hope, you use tap for the network and is right configured (no bad routes and dropping packets). After colinux was started, incrase the process priority for colinux-daemon.exe and for the network daemons. Some users sayed, it makes coLinux faster. Incrase the memory for coLinux. "mem=1000" is the highest you can use. > Maybe fiddling with "boot.ini" might help to find the core problem > > Some ideas: > > /burnmemory=1024 > /maxmem=1024 (better use burnmemory) > /3GB (or not?) > /userva=2900 (or less?) > /PAE (?) > /pcilock (?) Hm. An ugly idea. - Of curse, if you use /NOPAE and not all memory, then the coLinux driver would be faster. PAE handling is liddle more overhead. I think, it's not a good idea to downgrade the system memory to running faster :-( -- Henry N. |