[[Category:SPO600 Labs]]{{Admon/lab|Purpose of this Lab|In this lab, you will investigate the impact of different algorithms which produce the same effect. You will test and select one of two three algorithms for adjusting the volume of PCM audio samples based on benchmarking of two possible approaches.}}
== Lab 5 6 ==
1=== Background ===* Digital sound is typically represented, uncompressed, as signed 16-bit integer signal samples. Write There is are two different approaches to adjusting streams of samples, one each for the volume left and right stereo channels, at typical sample rates of 44.1 or 48 thousand samples per second per channel, for a sequence total of sound 88.2 or 96 thousand samplesper second (kHz). Since there are 16 bits (2 bytes) per sample, using different algorithms, in the C languagedata rate is 88. In each case2 * 1000 * 2 = 176,400 bytes/second (~172 KiB/sec) or 96 * 1000 * 2 = 192, you should take a series 000 bytes/second (~187.5 KiB/sec).* To change the volume of signed 16-bit integers representing sound waveform samples and multiply , each sample can be scaled (multiplied) by a floating point "volume scaling factor" , in the range of 0.000-00 (silence) to 1.00000 (full volume). It is recommended that one approach be * On a mobile device, the naive multiplication amount of the sample by the volume scaling factor, and the second approach be dramatically different (e.g., table lookup, multiplication by bit-shifting, memoization, or another approach)processing required to scale sound will affect battery life.
2. Test which approach is faster. Control the variables and use a large run of data (at least hundreds millions of samples). Use both [[SPO600 Servers|x86 and AArch64]] systems for testing - DO NOT compare results between the architectures (because they are different classes of systems) but DO compare the relative performance of the algorithms on each architecture. For example, you might note that "Algorithm I is NN% faster than Algorithm II on Architecture A, but NN% slower on Architecture B".=== Three Approaches ===
3Three approaches to this problem are provided: # The basic or Naive algorithm (<code>vol1.c</code>). This approach multiplies each sound sample by 0.75, casting from signed 16-bit integer to floating point and back again. Casting between integer and floating point can be [[Expensive|expensive]] operations.# A lookup-based algorithm (<code>vol2.c</code>). This approach uses a pre-calculated table of all 65536 possible results, and looks up each sample in that table instead of multiplying.# A fixed-point algorithm (<code>vol3.c</code>). This approach uses fixed-point math and bit shifting to perform the multiplication without using floating-point math. === Don't Compare Across Machines === In this lab, ''do not'' compare the relative performance across different machines, because the systems provided have a wide range of processor implementations, from server-class to mobile-class. However, ''do'' compare the relative performance of the various algorithms on the ''same'' machine. === Benchmarking === Get the files for this lab from one of the [[SPO600 Servers]] -- but you can perform the lab wherever you want (feel free to use your laptop or home system). Test on both an x86_64 and an AArch64 system. Review the contents of this archive:* <code>vol.h</code> controls the number of samples to be processed* <code>vol1.c</code>, <code>vol2.c</code>, and <code>vol3.c</code> implement the various algorithms* The <code>Makefile</code> can be used to build the programs Perform these steps:# Unpack the archive <code>/public/spo600-algorithm-selection-lab.tgz</code># Study each of the source code files and make sure that you understand what the code is doing.# '''Make a prediction''' of the relative performance of each scaling algorithm.# Build and test each of the programs.#* Do all of the algorithms produce the same output?#** How can you verify this?#** If there is a difference, is it significant enough to matter?#* Change the number of samples so that each program takes a reasonable amount of time to execute (suggested minimum 20 seconds, 1 minute or more is better).# Test the performance of each program.#* Find a way to measure performance ''without'' the time taken to perform the test setup pre-processing (generating the samples) and post-processing (summing the results) so that you can measure ''only'' the time taken to scale the samples. '''This is the hard part!'''#* How much time is spent scaling the sound samples?#* Do multiple runs take the same time? How much variation do you observe? What is the likely cause of this variation?#* Is there any difference in the results produced by the various algorithms?#* Does the difference between the algorithms vary depending on the architecture and implementation on which you test?#* What is the relative memory usage of each program?# Was your prediction accurate? === Deliverables === Blog about your experiments with a detailed analysis of your results, including memory usage, performance, accuracy, and trade-offs. Important Make sure you convincingly prove your results to your reader! -- Also be sure to explain what you're doing so that a reader coming across your blog post understands the context (in other words, don't just jump into a discussion of optimization results -- give your post some context). '''Optional - Recommended:''' Compare results across several '''implementations''' of AArch64 and x86_64 systems. Note that on different CPU implementations, the relative performance of different algorithms will vary; for example, table lookup may outperform other algorithms on a system with a fast memory system (cache), but not on a system with a slower memory system.* For AArch64, you could compare the performance on AArchie against the various class servers, or between the class servers and a Raspberry Pi 3 (in 64-bit mode) or an ARM Chromebook.* For x86_64, you could compare the performance of different processors, such as xerxes, your own laptop or desktop, and Seneca systems such as Matrix or lab desktops.
=== Things to consider ===
==== Design of Your Test Tests ==== * Most solutions for a problem of this type involve generating a large amount of data in an array, processing that array using the function being evaluated, and then storing that data back into an array. The test setup can take more time than the actual test! Make sure that you measure the time taken in the code under test function only -- you need to be able to remove the rest of the processing time from your evaluation.
* You may need to run a very large amount of sample data through the function to be able to detect its performance.
* If you do not use the output from your calculation (e.g., do something with the output array), the compiler may recognize that, and remove the code you're trying to test. Be sure to process the results in some way so that the optimizer preserves the code you want to test. It is a good idea to calculate some sort of verification value to ensure that both approaches generate the same results.
* You can test using actual sound data (see the tips section, below) or using generated data. If you're generating data, it is best to use a pseudo-random number generator which is seeded with the same value every time, so that each run processes the same data.* Be aware of what other tasks the system is handling during your test run, including software running on behalf of other users.
==== Analyzing Results =Tips ===* What is the impact {{Admon/tip|Analysis|Do a thorough analysis of various optimization levels on the software performance?* Does the distribution of data matter?* If samples are fed at CD rate results. Be certain (44100 samples per second x 2 channelsand prove!), can both algorithms keep up?* What is that your performance measurement ''does not'' include the memory footprint generation or summarization of each approach?* What is the performance of each approach?* What is test data. Do multiple runs and discard the energy consumption of each approach? (What information do you need outliers. Decide whether to calculate this?)* Xerxes and Betty have different performance profilesuse mean, minimum, so it's not reasonable to compare performance between or maximum time values from the machinesmultiple runs, but it is reasonable to compare the and explain why you made that decision. Control your variables well. Show relative performance of the two algorithms in each contextas percentage change, e.g. Do you get similar results?* What other optimizations can be applied to , "this problem?approach was NN% faster than that approach".}}
=== Competition ==={{Admon/tip|Non-Decimal Notation|In this lab, the number prefix 0x indicates a hexadecimal number, and 0b indicates a binary number, in harmony with the C language.}}* How fast {{Admon/tip|Time and Memory Usage of a Program|You can you scale 500 million int16 PCM sound samples?get basic timing information for a program by running <code>time ''programName''</code> -- the output will show the total time taken (real), the amount of CPU time used to run the application (user), and the amount of CPU time used by the operating system on behalf of the application (system). The version of the <code>time</code> command located in <code>/bin/time</code> gives slightly different information than the version built in to bash -- including maximum resident memory usage: <code>/bin/time ''./programName''</code>}}
=== Tips ===
{{Admon/tip|SOX|If you want to try this with actual sound samples, you can convert a sound file of your choice to raw 16-bit signed integer PCM data using the [http://sox.sourceforge.net/ sox] utility present on most Linux systems and available for a wide range of platforms.}}
{{Admon/tip|Stack Limitstdint.h|Fixed-size, non-static arrays will be placed in the stack space. The size of the stack space is controlled by per-process limits, inherited from the shell, and adjustable with the <code>ulimitstdint.h</code> command. Allocating an array larger than the stack header provides definitions for many specialized integer size limit will cause a segmentation fault, usually on the first write. To see the current stack limit, use <code>ulimit -s</code> (displayed value is in KB; default is usually 8192 KB or 8 MB)types. To set the current stack limit, place a new size in KB or the keyword Use <code>unlimitedint16_t</code>after the <code>for 16-s</code> argument.<br /><br />Alternate (and preferred) approach: allocate the array space with <code>malloc()</code> or <code>calloc()</code>bit signed integers.}}
{{Admon/tip|stdint.hScripting|The <code>stdint.h</code> header provides definitions for many specialized integer size types. Use <code>int16_t</code> for 16-bit signed integers.bash scripting capabilities to reduce tedious manual steps!}}
