Using Audacity As A Benchmark

Help for Audacity on Windows.
Forum rules
ImageThis forum is for Audacity on Windows.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".


Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
Post Reply
DangerofDeath
Posts: 2
Joined: Fri Nov 16, 2012 8:45 pm
Operating System: Please select

Using Audacity As A Benchmark

Post by DangerofDeath » Fri Nov 16, 2012 9:16 pm

Hey guys,

So I work for a computer hardware review website and I'd like to use Audacity as a benchmark in future reviews. The issue that I am having is finding a task in Audacity that would be limited by the performance of the CPU, rather than by memory size or I/O bandwidth of the system.

I should mention that I am using a Windows 7 x64 SP1 system and running Audacity version 2.0.2.

Any suggestions?

kozikowski
Forum Staff
Posts: 69374
Joined: Thu Aug 02, 2007 5:57 pm
Operating System: macOS 10.13 High Sierra

Re: Using Audacity As A Benchmark

Post by kozikowski » Sat Nov 17, 2012 4:45 am

Audacity performance tends to flatten out once the minimum required system speeds are met. It's always memory and drive problems. I don't think Audacity has been CPU bound in years.

A favorite of ours is Gaussian Blur in Photoshop. That always takes time because it puts a serious strain on the system.

Koz

Gale Andrews
Quality Assurance
Posts: 41761
Joined: Fri Jul 27, 2007 12:02 am
Operating System: Windows 10

Re: Using Audacity As A Benchmark

Post by Gale Andrews » Sat Nov 17, 2012 8:35 am

DangerofDeath wrote:So I work for a computer hardware review website and I'd like to use Audacity as a benchmark in future reviews. The issue that I am having is finding a task in Audacity that would be limited by the performance of the CPU, rather than by memory size or I/O bandwidth of the system.
Resampling? Change the project rate bottom left to something very different from the track rate, then Tracks > Resample.


Gale
________________________________________FOR INSTANT HELP: (Click on Link below)
* * * * * Tips * * * * * Tutorials * * * * * Quick Start Guide * * * * * Audacity Manual

steve
Site Admin
Posts: 81627
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu

Re: Using Audacity As A Benchmark

Post by steve » Sat Nov 17, 2012 9:17 am

The processed sound quality is not really affected by hardware. With slow hardware processing tracks just takes longer than with a fast machine, but the end result is identical.

Hardware, drivers and hardware configuration can have a big effect on playback quality. Trying to play a lot of tracks on a slow machine can cause the sound to break up and stutter. The problem tends to be worst when doing "overdub recording" (recording one track while playing back others). Measuring this could be difficult on a modern computer unless it is seriously under powered or only just meets minimum system requirements. You may need a lot of audio tracks before it starts stuttering. A data bottleneck anywhere in the system may cause stuttering and skips (see here: http://manual.audacityteam.org/man/FAQ: ... ting#skips)
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)

pshute
Posts: 181
Joined: Sat Feb 18, 2012 9:39 am
Operating System: Please select

Re: Using Audacity As A Benchmark

Post by pshute » Fri Nov 30, 2012 10:28 pm

Spectrograms use a fair bit of CPU time when the FFT window size is large. I think this is all done in memory, but it might need to access the disk to access the next bit of audio.

You could display an audio file with, say, 2 minutes showing, as a spectrogram with the window set to 32768, and see how long it takes to refresh the screen when you press Page Up to scroll a page to the right. I don't know if the contents

If it's still not slow enough, duplicate the track a few times and display them all as spectrograms.

The spectrogram parameters are in the Preferences, in the Spectrograms section.

Post Reply