Renoise & CPU load (an imperial art of benchmarking)

General Discussion
1

Let us gather some essential information. Since now all essential driver systems are supported for the most common operation systems on a PC, we shall collect the amount of CPU usage.

On a Windows 10 PC with 48 Mo on an I7 3,6 gHz and a 10 track mod (1 is a send) at 48 kHz you got:

An average CPU load about 34 % using ASIO on an external device (native). Buffer: 128 samples.

An average CPU load about 26 % using WASAPI on an external device.

An average CPU load about 24 % using direct sound on an external device.

An average CPU load about 31 % using ASIO on an internal device (realtek & ASIO4all).

An average CPU load about 26 % using WASAPI on an internal device.

An average CPU load about 25 % using direct sound on an internal device.

I could imagine, I created 36 tracks with an amount of 25 % at 44.1 kHz using AFA and a crappy Lenovo Ideapad (Realtek) 12 years ago.

I couldn`t test it using port audio.

2

On my Windows 11 System i never came above around 25% CPU usage with my AMD Ryzen 7 2700X 3,7 GHz 8 core (16 threads) CPU and 32 Gigs RAM.
And i use a lot heavy VSTs in my projects. It also depends a lot if your interfaces have good programmed drivers. It also depends on the used buffer sizes and also on the used samplerate.

3

Shame on me. I should have stated the buffer sizes.

4

Please use the rebench_x256.xrns for something similar to an real benchmark

1 Like
5

Exactly this, you can’t benchmark without a shared project.
Be interesting to see what the Pi400 can do.

6

What about FL Studio ASIO driver? I use it as a standard on my laptop. Works perfectly on the most min buffer size “256” - 48000 hz as a sample rate - . Crackles start to appear when using more than 18 heavy vst synths like Massive and Viral (together) with a lot of automated parameters. When crackles and glitches appear, i just rise the buffer size at one position ( from 256 to 512 ) and etc

Ps, a lot of factors can affect the CPU load and buffer size Capacity, like Background Active windows services, such as “Realtek audio.exe” or “Nahemic Server”, “Dolby support” … … Any (Side agent) that launches with your DAW as a plugin parallel supporter “Waves Pluginserver.exe” or “Arturiaportal.exe”, any background processes such as Planned background disk defragmentations or any kind of backgrounds scans, indexing or antivirus events …

Win10*AMD Ryzen 7-4800h 3.5mhz-16cores.16gbrm

7

Where can i get this file?

8

The project is rather lame, just a sketch of a remix of an old track of mine.
I’ve to buy some new data volume and then I can share it here. But don`t expect much.

9

You could have used the forum search yourself :stuck_out_tongue:

10

Renoise 3.4.1 (multicore = on / pdc = on)

142

Audio UMC Asio running at 48 kHz.

Buffersize: 128 samples (~2,7 ms).

OS: Win 10 Pro 21H2 / .1620

Board: MS-7B48 (MSI Z370-A Pro)

BIOS-Version/-Datum American Megatrends Inc. 2.C0, 04.06.2020

SMBIOS-Version 2.8

Processor: Intel(R) Core™ i7-9700K CPU @ 3.60GHz, 3600 MHz, 8 Kern(e), 8 logische(r) Prozessor(en)

RAM: Installierter physischer Speicher (RAM) 48,0 GB (DDR4) 1,2 gHz Dram / Uncore ~4,3 gHz

Pagefile: Größe der Auslagerungsdatei 14,0 GB

Gfx: Intel UHD 630 / Nvidia RTX2080 (8 GB)

Monitors: Benq SE3 / Noname running at 1920 x 1080 (hdmi / vga).

The test stopped at 68 % due to activated overload prevention in the preferences.

The test is based on direct sound and internal Renoise fx, so I should have a look at the other options again.

11

Since you mentioned the different audio drivers, is there a difference in benchmark values for those?

12

Seems to be so. This time I setup the overload protection to 91 % in the preferences.

UMC 404 using Jackrouter (Q’tJack) in Windows 10, 48 kHz, 128 k, dithering

195 Points.

UMC 404 using WASAPI (shared) in Windows 10, 44100 Hz, 384 k, dithering

227 Points.

UMC 404 using directX in Windows 10, 44100 Hz, 35 ms, dithering

257 Points. It ran through.

Realtek (MSI driver) using WASAPI (shared) in Windows 10, 48000 Hz, 512 k, dithering

257 Points. It ran through, although crackling and so on began at 190.

Realtek (MSI driver) using directX in Windows 10, 44100 Hz, 35 ms, dithering

257 Points. It ran through without crackling or else

Realtek (MSI driver) using Realtek Asio in Windows 10, 48000 Hz, 288 samples, dithering

238 Points. Crackling began at 170+.

Realtek (MSI driver) using FL Studio Asio in Windows 10, 48000 Hz, 256 samples, dithering

257 Points. It ran through. Crackling appeared at 230+.

Someone requested my pretty lame project:
spacefrog

In this early stage it’s just a sketch. So griping about it is pretty useless. :wink:

1 Like