Performance tuning: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
Processor Utilization tools: |
Processor Utilization tools: |
||
*) Sysprof |
*) Sysprof |
||
*) OProfile (http://wiki.laptop.org/go/Oprofile_setup) |
*) OProfile (http://wiki.laptop.org/go/Oprofile_setup) |
||
*) Python profiling (http://wiki.laptop.org/go/Python_profiling) |
*) Python profiling (http://wiki.laptop.org/go/Python_profiling) |
||
Revision as of 14:30, 28 March 2007
Performance Tuning for OLPC
The OLPC is a very resource limited machine. Decreasing resource use on the OLPC translates into very tangible benefits such as more space on machine for user content, better system responsiveness, better better battery life. There are two broad categories been looking at: processor use and memory use.
Processor Utilization tools:
- ) Sysprof
- ) OProfile (http://wiki.laptop.org/go/Oprofile_setup)
- ) Python profiling (http://wiki.laptop.org/go/Python_profiling)
- ) SystemTap (http://wiki.laptop.org/go/Systemtap) (http://www.mail-archive.com/devel@laptop.org/msg03436.html)
- ) Valgrind's callgrind tool to get call graph information (http://www.valgrind.org/)
Storage Utilization
- ) Valgrind's massif tool to examine memory allocation (http://www.valgrind.org/)
- ) Reducing size of code (http://lovesunix.net/spaceoptimization.pdf)
- ) Improving shared libraries (http://people.redhat.com/drepper/dsohowto.pdf)
- ) Scripts to analyze file system and process memory use (http://people.redhat.com/berrange/olpc/image/)
- ) Scripts to analyze process memory map (http://people.redhat.com/berrange/olpc/performance/)