Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Early Linux 2.6.31 Kernel Benchmarks

  1. #1
    Join Date
    Jan 2007
    Posts
    15,652

    Default Early Linux 2.6.31 Kernel Benchmarks

    Phoronix: Early Linux 2.6.31 Kernel Benchmarks

    The Linux 2.6.31 kernel is still under active development until it is released later this quarter, but the merge window is closed and most of the work going on is to address bugs and other regressions within this massive code-base. Some of the key additions to the Linux 2.6.31 kernel include many graphics-related advancements (merging of the TTM memory manager, Radeon kernel mode-setting, Intel DisplayPort, etc), an ALSA driver for the Creative X-Fi, initial USB 3.0 support, file-system improvements, and much more. To see how the general system performance has been impacted by the new Linux kernel that is in development, we have a few benchmarks today.

    http://www.phoronix.com/vr.php?view=14022

  2. #2
    Join Date
    Apr 2009
    Posts
    565

    Default

    Same here. I am running 2.6.31rc2 on my eeepc (because it helps a lot with the Intel IGP). But boot time to a full KDE4 login (mostly reads from the ext4 fs on the SSD) went up from 86 secs to 105 secs or so. All this in Kubuntu 9.04.

    I hope these fs regressions get worked out before the kernel goes golden!
    Last edited by mendieta; 07-08-2009 at 11:44 AM.

  3. #3
    Join Date
    Dec 2007
    Location
    Edinburgh, Scotland
    Posts
    597

    Default Bug Reports

    Out of interest did you raise a bug report for the ext4 regression?

    Maybe you could write an article on how bug reports are dealt with and hopefully fixed

    Would be a lot more interesting than looking at graphs from the PTS

    Mike

  4. #4
    Join Date
    May 2008
    Posts
    13

    Default

    Do you know if the problem lays within their architectural changes or new EXT4 filesystem patches? Well, I guess it is still early to judge since it is only at RC2.

  5. #5
    Join Date
    Aug 2007
    Posts
    6,676

    Default

    Well pure rc2 is not that good, you need extra patches to make dm work or to compile with older gcc. Also vbox 3 as host has issues on some systems (somehow not all). I did not notice speed diverences yet as i did not do any benchmarks. Basically it is possible to build fglrx with patches without modifiying the kernel too, i just don't know if my patch is fully correct. At least i did not notice any extra problems over those already known when using fglrx 9-6 with 2.6.29+.

  6. #6

    Default

    I am using a custom-built image of 2.6.31-rc2 on Kubuntu Karmic alpha. With all of the drivers for the hardware I need compiled in (Literally, the only thing in the output of lsmod is nvidia) and all the stuff I dont need removed, it takes about 11 seconds to boot from scratch to KDM. Then, it takes another 30 or 35 to start KDE. (Somehow, it starts taking this long whenever I modify or remove the Network Manager plasma widget after installing.)

  7. #7
    Join Date
    Jan 2009
    Posts
    206

    Default

    Quote Originally Posted by thefirstm View Post
    I am using a custom-built image of 2.6.31-rc2 on Kubuntu Karmic alpha. With all of the drivers for the hardware I need compiled in...
    Nice, did you configure that by hand & trial and error or did you use some kind of a tool?

    Hmm I might try Unigine Tropics / UT2004 on kernels 2.6.20~2.6.24~2.6.29~2.6.30.1~git linux-2.6 and test some 3D.

  8. #8

    Default

    Quote Originally Posted by hax0r View Post
    Nice, did you configure that by hand & trial and error or did you use some kind of a tool?
    By hand, every bit of it :-) I started with the Ubuntu kernel configuration, then I changed the CPU settings to fit my system better (optimized for Core 2/later Xeon, SMT support off, AMD support off, etc) and then I went through set the drivers for all of my hardware to be compiled in, and I disabled a bunch of stuff I thought I would never use. It booted up the first time, but there were a few more modules I compiled in after that.

  9. #9
    Join Date
    Aug 2007
    Posts
    6,676

    Default

    You gain only compile time when you disable unused modules and a bit hd space. Your pc will not get faster that way. The different cpu optimization gives you basically no speed increase, maybe in some rare cases. You "feel" changes like a different sheduler but no optimisation settings. Btw. KDE 4 starts really slow, when you would test my own distro with KDE 3.5 as development version then you would see that. Kubuntu is very easy to beat in bootup time.

  10. #10

    Default

    I didn't expect to gain much speed by recompiling. My primary objective was to make the system boot faster, which I accomplished. By the way, I also changed from "Voluntary Preemption" to "Preemption" which makes my system respond better when under load. (So well, in fact, that sometimes I have trouble telling it is under load without looking at top.) And having a shorter compile time is nice, too. A stock Ubuntu kernel takes almost an hour to compile on my machine, if I remember correctly. Mine takes only 20 or 30 minutes. I know my startup is slow, it is because I have removed the default Plasma Widget Network Manager because it does not work. Whenever I do this, the system gets some configuration problem, and refuses to start quickly anymore.
    Last edited by thefirstm; 07-09-2009 at 03:02 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •