Gputest

No PC hardware will last forever. Over time, heavy usage can begin to burn out components like your processor and graphics card. If your display is starting to seem a little glitchy, it could be time to replace your graphics card with a newer model. Before you do that, you should consider checking your graphics card for problems by conducting a stress test. Here’s how you can stress test your graphics card on Linux.GL Mark 2GL Mark 2 may be a better choice for you if you’re looking for something a little more complex. It tests a wider variety of aspects, such as lighting, buffering, texturing, and more. Think of it as the much more comprehensive version of Glxgears. Luckily, it’s included with most Linux distros and called glmark2. Install it by using the following:Then, run it by entering the following into the terminal:All tests are run for ten seconds each with the frame rate counted individually. You get a final score based on all the tests. It’s an incredibly simple-to-use tool that provides impressively in-depth results. GpuTestThe next tool to conduct a GPU stress test on Linux is the GpuTest tool. This cross-platform tool is available for Linux, macOS and Windows. It’s actually several tools in one, running several different types of graphics tests to see how well your graphics card is performing.While the software is a little outdated, it’s still capable of running tests on your GPU. It also includes the well-known and popular FurMark tool, which in recent releases has become Windows-only.GpuTest also includes several benchmarking options which will give you information on performance speeds, temperatures and more.To install it on Linux, download the most recent release of GpuTest and unzip the file. From there, open a terminal window and type the following to start the GpuTest

2019 1:49 pm Location: holland Has thanked: 429 times Been thanked: 1466 times Contact: Re: My LiveUSB DogLinux Bookworm build for hardware testing (nvidia-drivers, GPUTest) Post by fredx181 » Mon Oct 21, 2024 5:27 pm gumanzoy wrote: Mon Oct 21, 2024 4:57 pmBuild optional/nv340.108.squashfs and optional/nv390.157.squashfs modulesBoot DogLinux dog load=dkms;headersCode: Select allecho "deb sid contrib non-free" >> /etc/apt/sources.listapt updateCode: Select allapt -y install nvidia-legacy-340xx-driver libgles1-nvidia-legacy-340xx libgles2-nvidia-legacy-340xx libnvidia-legacy-340xx-cfg1 nvidia-legacy-340xx-smiI always hesitate to mix stable with unstable, do you think this is safe ? (even if it's just temporary to have sid repo in sources.list it may give trouble from what I experienced)edit: or if it works ok for the purpose of just creating a .squashfs module, shouldn't it be better to remove the sid repo after done ? gumanzoy Posts: 143 Joined: Mon May 03, 2021 3:38 pm Has thanked: 27 times Been thanked: 37 times Contact: Re: My LiveUSB DogLinux Bookworm build for hardware testing (nvidia-drivers, GPUTest) Post by gumanzoy » Mon Oct 21, 2024 5:43 pm fredx181 wrote: Mon Oct 21, 2024 5:27 pmI always hesitate to mix stable with unstable, do you think this is safe ? (even if it's just temporary to have sid repo in sources.list it may give trouble from what I experienced)edit: or if it works ok for the purpose of just creating a .squashfs module, shouldn't it be better to remove the sid repo after done ?Yes. rm -rf /tmp/*/etc/apt before create module. I do it by file-manager, and i don't described each thing, so it is not full complete howto, sorry.But better to look at contents of my created modules to check if some file needs to keep or needs to be deleted.None of my modules have /etc/apt/sources.listAnd, it is important. I don't add sid main, add only sid non-free and sid non-free-firmware for creating firmware modules. All of this is temporary.nvidia-legacy-340xx-driver and nvidia-legacy-390xx-driver present only in sid repo.edit: i edit post, and add rm -rf etc/apt to makes it is pretty clear.edit2: sid contrib don't need. Only need sid non-free.But nvidia-settings-legacy debs should get rebuilded for bookworm. It is need to fix dependency problem. PocketHandyBox (Debian 12 "Bookworm" with NVIDIA drivers OOTB) gumanzoy Posts: 143 Joined: Mon May 03, 2021 3:38 pm Has thanked: 27 times Been thanked: 37 times Contact: Re: My LiveUSB DogLinux Bookworm build for hardware testing (nvidia-drivers, GPUTest) Post by gumanzoy » Sat Nov 02, 2024 5:18

Graph bar means FASTEST time in SECONDS.) WHAT THE 2014 DUAL-CORE MAC MINI DOES BETTER The RED bar in the graphs signifies the fastest Mac mini Geekbench 3 - SINGLE-CORE TEST Primate Labs' cross-platform processor benchmark uses a scoring system. Workloads simulate real-world scenarios. The overall score is an amalgam of Integer, Floating Point, and Memory performance tests. (RED bar means FASTEST Score.) Final Cut Pro X 10.1.3 We imported a two minute 1440x1080 Apple ProRes 422 video clip. The Gaussian Blur effect is GPU intensive. (RED graph bar means FASTEST time in SECONDS.) LuxMark This is an OpenCL benchmark. We rendered the Sala scene using GPUs only. (RED graph bar means FASTEST in Thousands of Samples per Second.) GPUtest - FurMark This is a very intensive OpenGL benchmark that uses fur rendering algorithms to measure the performance of the graphics card. Fur rendering is especially adapted to overheat the GPU and that's why FurMark is also a perfect stability and stress test tool for the graphics card. We ran the test at 640x480 Windowed with anti-aliasing disabled. (RED bar means FASTEST in Frames Per Second.) GPUtest - TessMark Tessellation is the ability of the GPU to divide a polygon into smaller ones (according to the tessellation level factor) in order to increase polygon density: the higher the tessellation level, the higher the polygon density. The higher the tessellation level, the more GPU processing power is required. We chose 16 levels (usually the max that games use) at 640x480 Windowed with anti-aliasing disabled. (RED bar means FASTEST in Frames Per Second.) ANALYSIS For multi-core CPU intensive tasks, the Quad-Core 2012 Mac mini excelled even with a lower core clock speed. The 'beating' would have been even worse if we had access to the CTO 2.6GHz Quad-Core i7 Mac mini from