Re: [coLinux-devel] Slow performance.

[Óscar F. <of...@wa...>]

Henry Nestler <Hen...@Ar...> writes:

> Óscar Fuentes wrote:
>> Henry Nestler <Hen...@Ar...> writes:
>> 
>>>> The test suite starts a process more than 1000 times, pipes the output
>>>> into the controlling process, etc. My experience shows that GNU/Linux is
>>>> more effective than Windows for this sort of tasks.
>>> Suggest from you, here is a test script, that only eceute some
>>> processes, without disk io:
>>> #!/bin/bash
>>>
>>> loop=10000
>>> while test $loop -gt 0
>>> do
>>>     x=`uname -r`
>>>     loop=$(($loop - 1))
>>> done
>>>
>>> Tested with Intel(R) Pentium(R) 4 Mobile CPU 1.80GHz
>>> 22.9s   native, kernel 2.6.17
>>> 89.7s   coLinux 0.8.0, kernel 2.6.22.18
>>>
>>> Can you run tis on WVware please?
>> 
>> 26.2 seconds
>> Pentium M 2.00 GHz
>> VMWare 6.0.0
>> Linux etch 2.6.18-5-686 #1 SMP
>
> Ok. And is not faster as my native.

Please note that VMWare was slightly faster than the host *WindowsXP*
system for the same operation (running a test suite that requires
executing more than 1000 times the same process). If GNU/Linux is more
efficient than WindowsXP for this task, as I suspect, it is expected
that your native GNU/Linux is faster than my VMWare GNU/Linux guest,
even if my processor is a bit faster.

BTW, your shell script runs on 87.5 seconds on my coLinux install.

> An other PC: I have 17.1s on Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz. Runs
> only on one core and with 1.6GHz (2.6.22.5-31 SuSE 10.3 native)
>
>> I can't test it on coLinux, because I corrupted fstab while trying to
>> mount with noatime: I made a typo (noattime) and now the file system
>> mounts read-only. umount does not work, nor mount -o remount, etc.
>> 
>
> By the while "noatime" does not improve speed.

Same here.

-- 
Oscar