Announcement

Collapse
No announcement yet.

1080p Linux Gaming Performance - NVIDIA 415.22 vs. Mesa 19.0-devel RADV/RadeonSI

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #41
    Originally posted by debianxfce View Post
    There is no reason to wait bugs travelling down to your older kernels.
    Oh, there are many many reasons to wait, everybody wait . People are not perfect, making errors all the time. But if you are claiming otherwise then we fundamentally disagree

    For example, I sold my 6 months old HDMI only monitor when I noticed that the display port gets more attention.
    Cool that your business do well, still that is not for everybody and you are not smart. With army of such ingorants world would go nowhere

    There is nothing wrong with HDMI only monitors anyway, that is yet another reason for you to continue your trolling poem
    Last edited by dungeon; 12-17-2018, 07:53 AM.

    Comment


    • #42
      Originally posted by debianxfce View Post

      There are memory holes and unfreed memory objects in your whole system...
      Sell that to someone else, i don't give one single cent to that blah, blah

      Comment


      • #43
        Originally posted by debianxfce View Post
        So use latest software in your whole system.
        No one listen to that, i don't too. All what most people wants and need are fucking drivers, as stable as possible and nothing much else to move on.

        Some needs them more often, others not so much - maybe as much as something as much often from git every 10 days is needed (particulary for gamers for new game releases and no one else), other needs them only quarterly, third ones semi-annualy, forth ones are good with just one annualy and so on

        So who cares, if you use 30 to 50 driver builds annually or just one Gamers needs them more often, while else are fine with one or two.

        You are just pissed when using your old Mesa and kernels.
        Mine kernel is not old, it is latest released one, my mesa is also not old it is latest released one too That is what you are on, if you wanna roll.

        See, most rolling people are fine with 4-5 drivers and kernels switches annually as that is what majorly happen and nothing much else Non rolling are fine even with one annually or going further longterm where most linux kernel users are anyway

        But if you wanna troll instead to roll releases and not random git-asses , meanwhile you use git just to troll and for nothing else. Neither you are tester nor developer, nothing - just a baby troll
        Last edited by dungeon; 12-17-2018, 08:54 AM.

        Comment


        • #44
          Originally posted by clapbr View Post

          there is amdvlk-pro - same as amdvlk but with a closed source shader compiler. If you open the 18.50 amdgpu-pro .deb pkg you will find both vulkan-amdgpu-pro_18.50-708488_amd64 and vulkan-amdgpu_18.50-708488_amd64
          I thought you might have meant that. AFAIK, pieces from pro aren't made to be interchangeable with non-pro variants.

          This might be a crazy suggestion, but since you're running fairly up-to-date software (I do have some reservations there), have you considered installing one of the distributions officially supported by amdgpu-pro? If the pro shader compiler helps, maybe the rest of it will too.

          As for those reservations -- unless you're running some really new hardware and it's absolutely necessary, you probably don't need daily mesa builds. I have to suggest reverting back to your distro's stable packages and removing any pro components (a complete reinstall probably wouldn't hurt). If you're running an older LTS distro and you're using nightlies to get updates, it might be worth looking into Antergos or Manjaro to get a combination of stability and up-to-date packages.

          If you really want to use mesa nightlies, you might try taking a page from the debianxfce playbook and try the AMD testing kernel.

          Without hardware and OS specifics, it's kind of hard to help outside of generic suggestions like "delete the shader cache" and "check governors".

          Comment


          • #45
            Originally posted by clapbr View Post

            Pretty sure it is not a config issue, at least not something simple like cpu governor. My 6 cores (w/ 12 HT) are locked at 4ghz, GPU locked at high state, daily builds for mesa, latest xf86-video, libdrm, kernel. I also have pretty good cooling everywhere, so nor the CPU/GPU are throttling.

            I play civ6 on high though, but something consistent in all games that stutter is that reducing quality doesn't change the stuttering in any way. Interestingly it also doesn't show on screen capture, but it is pretty obvious in person. In dxvk games I've switched from radv to a ripped amdvlk-pro from ubuntu package and it usually gets a bit less fps but a lot less stuttering. Worse case is anything gallium-based, in some games glthread helps a bit but it still seems to not use all available hardware resources efficiently, possibly soft bottlenecks.
            Configure xorg.conf to enble tearfree. it's not usually enabled by default and is almot certainly exactly what you are seeing.

            Comment


            • #46
              @dungeon
              It is pointless to discuss with debianxfce.
              Only he is right and the only true system is a Frankendebian with unreleased kernel and software from the git. That's why he has so much success with his distribution, if you look at the number of installed systems.

              Comment


              • #47
                Michael

                good tests

                At simple seek seems nvidia use better cpu at 1080p

                In performance related stay more or less similar but amd needs improve seriously radeon tdp (maybe 7nm solve some of that)

                Comment


                • #48
                  @towo2099

                  4.18 kernel release and AMDGPU driver got GPU burning feature. While 4.19 kernel release got EXT4 corruptions

                  Situation is that even first few point releases are not so stable, but no he even recommends first RC to everybody Fu*king troll
                  Last edited by dungeon; 12-17-2018, 11:06 AM.

                  Comment


                  • #49
                    Originally posted by TemplarGR View Post
                    What? You must be young. A decade ago you could game 1080p/60fps maxed settings for AAA games with a 200 euro/dollar gpu. These days you need at least double that. GPUs are still ridiculously expensive. Things will only get better once AMD and Intel release gaming APUs that can replace the sub 200 dGPU market.
                    This doesn't seem quite accurate. My gaming rig has a two year old $199 Rx 480 card, and hits 100+ fps @ 1080p and Ultra settings on pretty much every recent AAA game. Paired with a 144Hz FreeSync monitor (Viewsonic XG2402) it's a silky buttery smooth experience, with no tearing, no stuttering, just smooooooth.

                    Just as impressive I think, is the fact that my mobo and cpu are from 2012, with DDR3 memory. Why spend money to upgrade when I'm gaming at 100+ fps of beautiful freesync goodness?

                    Those with deeper pockets can go 1440p or 4k, but 1080p is a great way for those on a budget to enjoy a premium experience.
                    Last edited by torsionbar28; 12-17-2018, 11:44 AM.

                    Comment


                    • #50
                      Originally posted by clapbr View Post
                      Usually happens when I'm hitting mobs, but even walking around it does happen. It's also totally random, which makes it even more annoying since I can't reproduce it doing the same steps. It also varies game to game, Dungeons 3 for example gets better after I play it for 5-10m. Albion gets 300+ fps and ocasionally drops to 220 and stutters very briefly, and if turn vsync on the same thing happens, drops briefly from 60 to 54 and stutter.
                      This does sound like shaders being uncached at first (so you get compilation delay) and then cached after a while.

                      How often were you updating the open source drivers ?

                      Comment

                      Working...
                      X