Announcement

Collapse
No announcement yet.

GravityMark OpenGL/Vulkan Performance For NVIDIA RTX 30 vs. AMD Radeon RX 6000 Series

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

  • GravityMark OpenGL/Vulkan Performance For NVIDIA RTX 30 vs. AMD Radeon RX 6000 Series

    Phoronix: GravityMark OpenGL/Vulkan Performance For NVIDIA RTX 30 vs. AMD Radeon RX 6000 Series

    A few days ago I wrote about GravityMark as a new cross-API GPU benchmark from a former Unigine developer. Being curious about the Linux GPU driver performance for this benchmark that is focused on delivering maximum GPU acceleration support, I ran some benchmarks on the latest NVIDIA GeForce and AMD Radeon graphics cards with this benchmark for OpenGL and Vulkan.

    https://www.phoronix.com/vr.php?view=30270

  • #2
    Does anyone have problem starting GravityMark on Arch?

    Code:
    ./GravityMark.x64: error while loading shared libraries: libTellusim_x64.so: cannot open shared object file: No such file or directory
    E:   2.619 s: Client::read(): can't exec "./GravityMark.x64 -vk -ta 1 -a 50000 -fps 1 -info 1 -sensors 1 -benchmark 1" command

    Comment


    • #3
      Here are the results for my GTX 1660 Ti: https://www.techpowerup.com/forums/t...6/post-4543860

      For some reasons the test runs a lot faster under Windows 10 than under Linux. You'd think that Vulkan, being very close to HW, should have similar performance under different OS'es but that's not the case.

      Lastly, the OpenGLES test crashes NVIDIA drivers: https://forums.developer.nvidia.com/...drivers/181025

      NVIDIA is yet to confirm or fix the problem.

      Originally posted by mattia.b89 View Post
      Does anyone have problem starting GravityMark on Arch?

      Code:
      ./GravityMark.x64: error while loading shared libraries: libTellusim_x64.so: cannot open shared object file: No such file or directory
      E: 2.619 s: Client::read(): can't exec "./GravityMark.x64 -vk -ta 1 -a 50000 -fps 1 -info 1 -sensors 1 -benchmark 1" command

      Here's a solution: https://www.techpowerup.com/forums/t...6/post-4542862

      I've been told by the CEO that they will fix the issue in the next public release.

      Comment


      • #4
        Strange how AMD's performance scaled worse as resolution went up. Normally I would think it'd get better, seeing as they have more VRAM. But, perhaps this benchmark doesn't really stress VRAM much.

        Comment


        • #5
          Originally posted by schmidtbag View Post
          Strange how AMD's performance scaled worse as resolution went up. Normally I would think it'd get better, seeing as they have more VRAM. But, perhaps this benchmark doesn't really stress VRAM much.
          It might be more about memory bandwidth than capacity. Nvidia GPU have the faster GDDR6X, which I think is what helps them a lot.

          Comment


          • #6
            Originally posted by mattia.b89 View Post
            Does anyone have problem starting GravityMark on Arch?

            Code:
            ./GravityMark.x64: error while loading shared libraries: libTellusim_x64.so: cannot open shared object file: No such file or directory
            E: 2.619 s: Client::read(): can't exec "./GravityMark.x64 -vk -ta 1 -a 50000 -fps 1 -info 1 -sensors 1 -benchmark 1" command
            Need to set the LD_LIBRARY_PATH for the location of the library.
            Michael Larabel
            http://www.michaellarabel.com/

            Comment


            • #7
              birdie Michael thanks








              Comment


              • #8
                Works good @ Ubuntu 21.04, Mesa 21.1.2 - kisak-mesa PPA + RADV:
                Code:
                wget https://tellusim.com/download/GravityMark_1.1b.run
                bash GravityMark_1.1b.run --noexec --target GravityMark_1.1b
                cd GravityMark_1.1b/bin/
                LD_LIBRARY_PATH=./ ./Browser.x64 -root browser/ ../browser.zip

                Comment


                • #9
                  [email protected]~/GravityMark_1.1_linux$ ./run_windowed_vk.sh
                  M: 0 us: GravityMark Started
                  M: 20.62 ms: ../data.zip: 313 files
                  M: 20.83 ms: Temporal antialiasing
                  WARNING: radv is not a conformant vulkan implementation, testing use only.
                  MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete
                  M: 1.150 s: Build Date: Jun 18 2021
                  M: 1.150 s: Build Info: release; vk=1; gl=45; gles=32
                  M: 1.223 s: System: Linux 5.12.10-xanmod1 x86_64 GNU/Linux
                  M: 1.223 s: Kernel: #0~git20210610.d262d74 SMP PREEMPT Thu Jun 10 13:59:27 UTC 2021
                  M: 1.223 s: Memory: 15.52 GB
                  M: 1.223 s: Uptime: 4 days 1:53
                  M: 1.223 s: CPU: Intel(R) Core(TM) i7-3635QM CPU @ 2.40GHz
                  M: 1.223 s: Device: VEN_8086&DEV_0166&SUBSYS_C0E6144D
                  M: 1.223 s: GPU: [AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X/M370X]
                  M: 1.223 s: Device: VEN_1002&DEV_6821&SUBSYS_C0E6144D
                  M: 1.223 s: Memory: 2.00 GB
                  M: 1.231 s: Desktop: 1920x1080 1.0
                  M: 1.231 s: Screen 0: 1920x1080 0 0 eDP-1
                  M: 1.231 s: Creating 1600x900 Vulkan Window
                  M: 1.392 s: Using Fetch mode
                  ./run_windowed_vk.sh: line 30: 3094862 Illegal instruction ./GravityMark.x64 -temporal 1 -fps 1 -info 1 -sensors 1 -benchmark 1 -vk
                  [email protected]~/GravityMark_1.1_linux$
                  [email protected]~/GravityMark_1.1_linux$ ./run_windowed_gl.sh
                  M: 0 us: GravityMark Started
                  M: 19.69 ms: ../data.zip: 313 files
                  M: 19.89 ms: Temporal antialiasing
                  M: 84.20 ms: Build Date: Jun 18 2021
                  M: 84.30 ms: Build Info: release; vk=1; gl=45; gles=32
                  M: 132.52 ms: System: Linux 5.12.10-xanmod1 x86_64 GNU/Linux
                  M: 132.55 ms: Kernel: #0~git20210610.d262d74 SMP PREEMPT Thu Jun 10 13:59:27 UTC 2021
                  M: 132.58 ms: Memory: 15.52 GB
                  M: 132.62 ms: Uptime: 4 days 1:53
                  M: 132.65 ms: CPU: Intel(R) Core(TM) i7-3635QM CPU @ 2.40GHz
                  M: 132.68 ms: Device: VEN_8086&DEV_0166&SUBSYS_C0E6144D
                  M: 140.52 ms: Desktop: 1920x1080 1.0
                  M: 140.65 ms: Screen 0: 1920x1080 0 0 eDP-1
                  M: 140.73 ms: Creating 1600x900 OpenGL Window
                  X Error of failed request: GLXBadFBConfig
                  Major opcode of failed request: 152 (GLX)
                  Minor opcode of failed request: 34 ()
                  Serial number of failed request: 28
                  Current serial number in output stream: 25
                  [email protected]~/GravityMark_1.1_linux$
                  [email protected]~/GravityMark_1.1_linux$ ./run_windowed_gles.sh
                  M: 0 us: GravityMark Started
                  M: 19.68 ms: ../data.zip: 313 files
                  M: 19.88 ms: Temporal antialiasing
                  E: 30.88 ms: GLES:pen(): can't load OpenGLES library
                  Invalid or incomplete multibyte or wide character
                  E: 31.15 ms: GLESWindow::GLESWindow(): can't open OpenGLES
                  M: 31.25 ms: Build Date: Jun 18 2021
                  M: 31.32 ms: Build Info: release; vk=1; gl=45; gles=32
                  M: 78.67 ms: System: Linux 5.12.10-xanmod1 x86_64 GNU/Linux
                  M: 78.73 ms: Kernel: #0~git20210610.d262d74 SMP PREEMPT Thu Jun 10 13:59:27 UTC 2021
                  M: 78.77 ms: Memory: 15.52 GB
                  M: 78.82 ms: Uptime: 4 days 1:54
                  M: 78.85 ms: CPU: Intel(R) Core(TM) i7-3635QM CPU @ 2.40GHz
                  M: 78.90 ms: Device: VEN_8086&DEV_0166&SUBSYS_C0E6144D
                  M: 86.64 ms: Desktop: 1920x1080 1.0
                  M: 86.78 ms: Screen 0: 1920x1080 0 0 eDP-1
                  M: 86.87 ms: Creating 1600x900 OpenGLES Window
                  E: 86.94 ms: GLESWindow::create_visual(): display is not opened
                  E: 87.64 ms: Window::create(): can't create context
                  E: 87.73 ms: GravityMark::create(): can't create Window for OpenGLES platform
                  V: 96.77 ms: Dialogs::create(): compile "/home/user/.tellusim/dialogs_gtk2_x64.so"
                  Package gtk+-2.0 was not found in the pkg-config search path.
                  Perhaps you should add the directory containing `gtk+-2.0.pc'
                  to the PKG_CONFIG_PATH environment variable
                  No package 'gtk+-2.0' found
                  Package gtk+-2.0 was not found in the pkg-config search path.
                  Perhaps you should add the directory containing `gtk+-2.0.pc'
                  to the PKG_CONFIG_PATH environment variable
                  No package 'gtk+-2.0' found
                  M: 103.57 ms: sh: 1: clang++: not found
                  M: 103.64 ms: sh: 1: clang++: not found
                  V: 103.75 ms: Dialogs::create(): compile "/home/user/.tellusim/dialogs_gtk3_x64.so"
                  Package gtk+-3.0 was not found in the pkg-config search path.
                  Perhaps you should add the directory containing `gtk+-3.0.pc'
                  to the PKG_CONFIG_PATH environment variable
                  No package 'gtk+-3.0' found
                  Package gtk+-3.0 was not found in the pkg-config search path.
                  Perhaps you should add the directory containing `gtk+-3.0.pc'
                  to the PKG_CONFIG_PATH environment variable
                  No package 'gtk+-3.0' found
                  M: 110.40 ms: sh: 1: clang++: not found
                  M: 110.47 ms: sh: 1: clang++: not found
                  V: 110.61 ms: Dialogs::create(): compile "/home/user/.tellusim/dialogs_qt5_x64.so"
                  qtchooser: could not exec '/usr/lib/qt5/bin/qmake': No such file or directory
                  qtchooser: could not exec '/usr/lib/qt5/bin/qmake': No such file or directory
                  M: 119.82 ms: sh: 1: clang++: not found
                  M: 119.89 ms: sh: 1: clang++: not found
                  V: 120.04 ms: Dialogs::create(): compile "/home/user/.tellusim/dialogs_qt4_x64.so"
                  qtchooser: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': No such file or directory
                  qtchooser: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qmake': No such file or directory
                  M: 129.55 ms: sh: 1: clang++: not found
                  M: 129.64 ms: sh: 1: clang++: not found
                  V: 129.78 ms: Dialogs::create(): compile "/home/user/.tellusim/dialogs_qt5_x64.so"
                  qmake: could not exec '/usr/lib/qt5/bin/qmake': No such file or directory
                  qmake: could not exec '/usr/lib/qt5/bin/qmake': No such file or directory
                  M: 138.57 ms: sh: 1: clang++: not found
                  M: 138.64 ms: sh: 1: clang++: not found
                  V: 138.75 ms: Dialogs::create(): compile "/home/user/.tellusim/dialogs_qt4_x64.so"
                  qmake: could not exec '/usr/lib/qt5/bin/qmake': No such file or directory
                  qmake: could not exec '/usr/lib/qt5/bin/qmake': No such file or directory
                  M: 148.42 ms: sh: 1: clang++: not found
                  M: 148.49 ms: sh: 1: clang++: not found
                  E: 148.65 ms: Dialogs:pen(): can't load dialogs library
                  No such file or directory
                  M: 148.72 ms: DialogMessage(GravityMark): Screen 0: 1920x1080 0 0 eDP-1
                  Creating 1600x900 OpenGLES Window
                  GLESWindow::create_visual(): display is not opened
                  Window::create(): can't create context
                  GravityMark::create(): can't create Window for OpenGLES platform

                  Initialization error

                  M: 157.50 ms: GravityMark Finished
                  [email protected]~/GravityMark_1.1_linux$
                  Hm...
                  Last edited by reba; 18 June 2021, 03:20 PM.

                  Comment


                  • #10
                    Originally posted by reba View Post
                    Hm...
                    There is no AVX support on i7-3635QM. It's not, actually, required for the benchmark. It looks like we missed it.

                    There is a benchmark update at https://gravitymark.com where LD_LIBRARY_PATH modification is not required.

                    Comment

                    Working...
                    X