2
edits
Changes
→Project Plan
<b><font style="font-size:120%"> 0.1 Optimize and run a benchmark program specifically designed to make use of <code>glibc</code></font></b>
Any packages compiled for the beagleboards can be installed without optimization. So far, in the case of <code>cdot-beagleXM-0-3</code> packages are compiled without it. Without optimizations, software installed in a system can only run on optimal performance. In order to make use of ARMv7 architecture features, editing the <code>CFLAGS</code> to use <code>arm</code> optimization options will let the compiler attempt to improve the performance and/or code size of the program; resulting in a more efficient /faster system.
The goal of this release is to run a benchmark software named [http://en.wikipedia.org/wiki/Dhrystone Dhrystone] on <code>cdot-beagleXM-0-3</code> and record the results. Three (3) runs are required: '''No optimization''', '''Optimized for armv5tel''', and '''Optimized for armv7'''. The purpose of running dhrystone Dhrystone is listed belowchosen as the benchmark software for the following reasons:
<b><font style="font-size:100%">Reasons for using Dhrystone</font></b>
*Dhrystone numbers reflect the performance of the C compiler and libraries more so than the performance of the processor itself. (considered as a weakness of the program)
*Check if armv7 optimization options and armv5tel optimization options differ significantly in system performance boost
'''Test Result:'''
*Optimized for armv7 = 1034.82179852 DMIPS
The benchmark graph shows that optimization increased the overall performance of cdot-beagleXM-0-3 by '''36%'''. The results for both armv5tel and armv7 optimizations are the same. (It's safe to assume that the armv5tel glibc impacts the performance of C library dependent programs such as Dhrystone). The data gathered can be used as a reference for conducting 0.2 project release.
* 0.2
* 0.3
