"TMS320C55x DSP Library DSPLIB Programmer's Reference"

What DSPLIB Benchmarks are Provided / Performance Considerations5.1 What DSPLIB Benchmarks are ProvidedDSPLIB documentation includes benchmarks for instruction cycles andmemory consumption. The following benchmarks are typically included:Calling and register initialization overheadNumber of cycles in the kernel code: Typically provided in the form of anequation that is a function of the data size parameters. We consider thekernel (or core) code, the instructions contained between the _start and_end labels that you can see in each of the functions.Memory consumption: Typically program size in bytes is reported. Forfunctions requiring significant internal data allocation, data memory consumptionis also provided. When stack usage for local variables is minimum,that data consumption is not reported.For functions in which it is difficult to determine the number of cycles in the kernelcode as a function of the data size parameters, we have included directcycle count for specific data sizes.5.2 Performance ConsiderationsBenchmark cycles presented assume best case conditions, typically assuming:0 wait-state memory external memory for program and datadata allocation to on-chip DARAMno pipeline hitsA linker command file showing the memory allocation used during testing andbenchmarking in the Code Composer C55x Simulator is included under theexample subdirectory.Remember, execution speed in a system is dependent on where the differentsections of program and data are located in memory. Be sure to account forsuch differences, when trying to explain why a routine is taking more time thatthe reported DSPLIB benchmarks.5-2