Performance benchmark & stressing the hardware
I remember finding some tools (forgot names could perhaps re-find them) that stress / benchmarked a Linux OS -- but only the high-level disk I/O (nothing but fopen/fwrite/fread/fclose) ... nothing low level! This is the best way to test anyways!
After revisiting some of the performance stuff on this website and remembering my dubious flirtation with setpci (which improved performance some) but was entirely blind luck for the most part... this leads me to the idea of a more "serious" benchmarking of two or three components involved with Ardour
1) Sound performance
2) Disk performance
3) Video performance
Has anybody visited the idea of a mini-ardour-like benchmark+stressing program!?
Such a program should using the Jack daemon for access to hardware so you can also test your settings there. It should capture (and discard?) and playback (pink noise?) to all channels at the same time reading and writing to many files (user selected, like pick 25 read/25 write). It would create 25 "tracks" (broadcast wave files, 32-bit floating), then proceed to capture/playback audio and then read those tracks while writing more.
This would be the core program, to push bits (bytes) of dates around -- a lot of data to stress the machine.
An additional parent program would be something that scans IRQs, and PCI settings and make suggestions, test them, compare agains other settings and save the results. (for a particular level of "Stress"). Additionally, (optionally) screen updates (such as simulating sliders or level meters, etc.) ... Not sure all what should be included.
The goal is a program that can be command line set for various levels of disk, jack (sound) and video stressing. And a parent program that scans hardware and suggest changes and benchmarks changes (so you know if a change is better or worse!)
Just an idea. I hate to get into it, but I could attempt to write some of it however I am not a good C++ programmer (been lazy and using scripting languages like Bash and PHP now for too long).
I am not good at GTK, only done superficial SDL programming, and no sound (with or without Jack). I think something like this would be helpful!
This is just an idea.