Announcement

Collapse
No announcement yet.

2D slowness in r500 radeon EXA?

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

  • #16
    Originally posted by curaga View Post
    Is support for that difficult to implement? Can it happen before 1.6 is out?
    Not likely. Only very recent hw even supports a1 surfaces natively. I suppose you could do some tricks with color expansion on older hw, but core EXA would need a1 support first.

    Comment


    • #17
      some tricks with color expansion on older hw
      Is this how XAA handled it?

      Comment


      • #18
        XAA is mostly sw. It's faster in some cases because it doesn't even attempt to accelerate most things so there's no migration of data between vram and system ram (which is where you lose).

        Comment


        • #19
          Originally posted by agd5f View Post
          EXA has preformed well for me for a while now. xserver 1.5 should be fine for the most part. 1.6 mainly improves font rendering preformance. Are you using kde 4 by any chance? IIRC kde 4 uses render bits that aren't accelerated with EXA at the moment.
          Mmm... this could be the cause of KDE 4 running sluggishly with radeon with EXA and running amazingly fast with vesa.

          Comment


          • #20
            Originally posted by panda84 View Post
            Mmm... this could be the cause of KDE 4 running sluggishly with radeon with EXA and running amazingly fast with vesa.
            that's exactly why. kde4 uses a1 surfaces.

            Comment


            • #21
              Originally posted by agd5f View Post
              [cut] kde 4 did something similar and that's why it was slow. They should really be using a8 since both EXA and a lot more hardware can support a8.
              Sorry for the dumb question: did you contact the KDE team? Did you file a bug/wishlist report? What did they reply?

              Comment


              • #22
                Or maybe it's because you have EXAvsynch on. It might be just me, although I'm keen on doing some benchmarks, but I kind of notice that switching the option on and off makes a difference in resizing windows and switching between windows.

                Does anyone have any benchmarks on this already?

                Comment


                • #23
                  There's no reason to use EXAVSync if you want the fastest performance. It stalls the engine waiting to the vline to avoid tearing for EXA rendering. It has nothing to do with Xv, that is handled separately.

                  Comment


                  • #24
                    Yeah, but I want tear-free and fast performance . Otherwise I need to restart X each time when I switch between them.

                    Comment


                    • #25
                      I don't have EXAVsync enabled; the only option is "Accelmethod" "EXA".

                      Am I seeing tear-free display & XV because of not using compositing?

                      Comment


                      • #26
                        Originally posted by curaga View Post
                        I don't have EXAVsync enabled; the only option is "Accelmethod" "EXA".

                        Am I seeing tear-free display & XV because of not using compositing?
                        The Xv vline stuff is handled separately from EXA. Same process though.

                        Comment

                        Working...
                        X