 | Services - tools - models - for embedded software development |
|---|
| Services - tools - models - for embedded software development |
|---|
 |  | |
The raw load generated by the debugging script can be measured by
comparing the number of cycles taken using the script, with the
number of cycles taken when just loading the program and running to
completion. The results, using a server with no compiler
optimization (-O0) and no caching of memory or
SPRs (see Section 5.2) are shown in Table 5.1.
|
Run Description |
Cycles |
Time |
Performance |
|---|---|---|---|
|
No optimization, no cache, no debug script |
1,491,415 |
45.83 s |
33 kHz |
|
No optimization, no cache, with debug script |
12,593,861 |
374.02 s |
34 kHz |
Table 5.1. Load generated by the GDB debugging script.
As can be seen the debugging commands add over 11 million cycles to the server model in this baseline configuration.
| |  | |
| 5.1. Assessing Performance |  | 5.2. Caching SPR and Memory Access |