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

Thread: Until Re-Clocking Is Figured Out, Nouveau Remains Very Slow Against NVIDIA

  1. #1
    Join Date
    Jan 2007
    Posts
    14,620

    Default Until Re-Clocking Is Figured Out, Nouveau Remains Very Slow Against NVIDIA

    Phoronix: Until Re-Clocking Is Figured Out, Nouveau Remains Very Slow Against NVIDIA

    Up for sharing today are our benchmarks comparing the very latest open-source Nouveau graphics driver code (Linux 3.15 + Mesa 10.3-devel) against the proprietary NVIDIA Linux graphics driver to see how the two NVIDIA Linux drivers compare.

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

  2. #2
    Join Date
    Dec 2011
    Posts
    145

    Default How about a fair comparison

    Hi Michael,

    As a frequent reader, I really, really know that "Until Re-Clocking Is Figured Out, Nouveau Remains Very Slow Against NVIDIA", but would be very interested in a clock for clock comparison.
    I don't have any nvidia cards anymore, but when I last had the honor, I remember it was possible to set clock speeds manually (heck I did it as a manual power saving feature...). Plus a quick google search tells me it might be pretty well scriptable : http://guilleml.wordpress.com/2011/0...izer-on-linux/

    So how about it? I think it would be a pretty good performance comparison of the blob vs nouveau, even though not of a real world usecase.

    Serafean

  3. #3
    Join Date
    Jul 2009
    Posts
    250

    Default

    Quote Originally Posted by Serafean View Post
    Hi Michael,

    As a frequent reader, I really, really know that "Until Re-Clocking Is Figured Out, Nouveau Remains Very Slow Against NVIDIA", but would be very interested in a clock for clock comparison.
    I don't have any nvidia cards anymore, but when I last had the honor, I remember it was possible to set clock speeds manually (heck I did it as a manual power saving feature...). Plus a quick google search tells me it might be pretty well scriptable : http://guilleml.wordpress.com/2011/0...izer-on-linux/

    So how about it? I think it would be a pretty good performance comparison of the blob vs nouveau, even though not of a real world usecase.

    Serafean
    +1

    besides, when it is "silly" to compare these 2 on same low clock, then why bother to compare when the one has a considerably higher clock? thats just close to bullying.

  4. #4
    Join Date
    Sep 2013
    Posts
    16

    Default

    Quote Originally Posted by Serafean View Post
    Hi Michael,

    As a frequent reader, I really, really know that "Until Re-Clocking Is Figured Out, Nouveau Remains Very Slow Against NVIDIA", but would be very interested in a clock for clock comparison.
    I don't have any nvidia cards anymore, but when I last had the honor, I remember it was possible to set clock speeds manually (heck I did it as a manual power saving feature...). Plus a quick google search tells me it might be pretty well scriptable : http://guilleml.wordpress.com/2011/0...izer-on-linux/

    So how about it? I think it would be a pretty good performance comparison of the blob vs nouveau, even though not of a real world usecase.

    Serafean
    Heck yeah, we have Coolbits back. Let's stop this "Until Re-Clocking Is Figured Out, Nouveau Remains Very Slow Against NVIDIA" bullcrap. We all know that since ~2011.

  5. #5

    Default

    Quote Originally Posted by Serafean View Post
    Hi Michael,

    As a frequent reader, I really, really know that "Until Re-Clocking Is Figured Out, Nouveau Remains Very Slow Against NVIDIA", but would be very interested in a clock for clock comparison.
    I don't have any nvidia cards anymore, but when I last had the honor, I remember it was possible to set clock speeds manually (heck I did it as a manual power saving feature...). Plus a quick google search tells me it might be pretty well scriptable : http://guilleml.wordpress.com/2011/0...izer-on-linux/

    So how about it? I think it would be a pretty good performance comparison of the blob vs nouveau, even though not of a real world usecase.

    Serafean
    FTA: "For those that then suggest to run tests of the NVIDIA binary blob with the graphics cards intentionally under-clocked, that is rather silly too, given that no one would intentionally do this in practice and that when the GPU core and video memory frequencies are severely restricted we're not seeing the driver's full optimization abilities in full."

  6. #6
    Join Date
    May 2014
    Posts
    2

    Default Idea

    You can try to put clocks always at 3D frequency by BIOS editing, no?

  7. #7
    Join Date
    Nov 2012
    Location
    France
    Posts
    563

    Default

    Quote Originally Posted by prazola View Post
    You can try to put clocks always at 3D frequency by BIOS editing, no?
    This is possible, but:

    - VBIOS flashing is always risky (unless you have multiple VBIOS chips on your graphics card, like some overclocking-targeted cards),
    - you don't benefit from any power management (high noise and power usage all the time).

    Not to mention potential warranty issues (if you send your graphics card to warranty).

    Quote Originally Posted by Pepec9124 View Post
    Heck yeah, we have Coolbits back. Let's stop this "Until Re-Clocking Is Figured Out, Nouveau Remains Very Slow Against NVIDIA" bullcrap. We all know that since ~2011.
    We've always had CoolBits (eg. for fan control), what came back is overclocking support.

    It's a sad reality, Nouveau is mostly only suitable for people who do little to no 3D stuff (which may count more people than you may think).

  8. #8
    Join Date
    Dec 2012
    Posts
    526

    Default

    Quote Originally Posted by Michael View Post
    FTA: "For those that then suggest to run tests of the NVIDIA binary blob with the graphics cards intentionally under-clocked, that is rather silly too, given that no one would intentionally do this in practice and that when the GPU core and video memory frequencies are severely restricted we're not seeing the driver's full optimization abilities in full."
    The point is that, while reclocking is the elephant in the room, it is one elephant - and it dominates the conversation. And obviously the fact it still is not fixed means those working on Nouveau have hit a brick wall and repeating the same thing over and over won't give them the information to actually implement it. It would be new and interesting information to see how the Nouveau pipeline would perform in the absence of that elephant, though, because as the radoen driver demonstrates there are a lot of other performance characteristics besides clock speed.

  9. #9
    Join Date
    May 2014
    Posts
    2

    Default

    Quote Originally Posted by Calinou View Post
    This is possible, but:

    - VBIOS flashing is always risky (unless you have multiple VBIOS chips on your graphics card, like some overclocking-targeted cards),
    - you don't benefit from any power management (high noise and power usage all the time).

    Not to mention potential warranty issues (if you send your graphics card to warranty).
    We are looking for architecture supporting progress, power management will be tested when freq switching support arrive.

    VBIOS flash is not risky if you keep parameters between default ranges. A bad BIOS flash isn't a problem if you don't power off while writing the ROM.

  10. #10
    Join Date
    Dec 2011
    Posts
    145

    Default

    Quote Originally Posted by Michael View Post
    FTA: "For those that then suggest to run tests of the NVIDIA binary blob with the graphics cards intentionally under-clocked, that is rather silly too, given that no one would intentionally do this in practice and that when the GPU core and video memory frequencies are severely restricted we're not seeing the driver's full optimization abilities in full."
    No, no one would do that intentionally in practice. But you're missing the point of why we ask : the interesting information not present in your benchmarks is how well does the 3D driver work. And only the 3D driver, not other hw features (no one is asking for vdpau performance comparisons, and you're not doing them )
    The information from this would be "once recklocking works, we can expect about 60% of the blob's performance".
    I'm not telling you what to do, nor to do it often, just that it's somethin I (and apparently some others) would find interesting.
    And I maintain that not testing against an under-clocked blob is as silly as testing against and underclocked nouveau.

    Serafean.

Posting Permissions

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