Performance tuning: Difference between revisions
Jump to navigation
Jump to search
RafaelOrtiz (talk | contribs) (inner links) |
|||
| Line 1: | Line 1: | ||
== Performance Tuning for OLPC == |
== 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, |
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 battery life. There are two broad categories been looking at: processor use and memory use. |
||
Processor Utilization tools: |
Processor Utilization tools: |
||
| Line 9: | Line 9: | ||
* [[Systemtap]] (http://www.mail-archive.com/devel@laptop.org/msg03436.html) |
* [[Systemtap]] (http://www.mail-archive.com/devel@laptop.org/msg03436.html) |
||
* Valgrind's callgrind tool to get call graph information (http://www.valgrind.org/) |
* Valgrind's callgrind tool to get call graph information (http://www.valgrind.org/) |
||
Storage Utilization: |
Storage Utilization: |
||
| Line 17: | Line 18: | ||
* Scripts to analyze file system and process memory use (http://people.redhat.com/berrange/olpc/image/) |
* 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/) |
* Scripts to analyze process memory map (http://people.redhat.com/berrange/olpc/performance/) |
||
* Utility to analyze file sytem usage (http://www.pixelbeat.org/fslint/) |
|||
* Utility to analyze RAM usage (http://www.pixelbeat.org/scripts/ps_mem.py) |
|||
Revision as of 13:52, 29 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 battery life. There are two broad categories been looking at: processor use and memory use.
Processor Utilization tools:
- Sysprof (http://www.daimi.au.dk/~sandmann/sysprof/)
- Oprofile_setup
- Python_profiling
- 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:
- Memphis (http://dev.laptop.org/git.do?p=projects/soc-memphis)
- 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/)
- Utility to analyze file sytem usage (http://www.pixelbeat.org/fslint/)
- Utility to analyze RAM usage (http://www.pixelbeat.org/scripts/ps_mem.py)