Feature roadmap/General UI sluggishness: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (fix link to User:MarcoPesentiGritti)
No edit summary
Line 23: Line 23:


Suggestions from John Gilmore (e-mail here: http://lists.laptop.org/pipermail/devel/2008-December/021595.html) <br>
Suggestions from John Gilmore (e-mail here: http://lists.laptop.org/pipermail/devel/2008-December/021595.html) <br>
'''File read write performance'''
* Putting a swap partition on an SD card and seeing what it does for performance
* Putting a swap partition on an SD card and seeing what it does for performance
* Building an un-compressed JFFS2 filesystem (it's trivial with the tools used) and seeing what it does for performance
* Building an un-compressed JFFS2 filesystem (it's trivial with the tools used) and seeing what it does for performance
'''System memory usage optimization'''
* Running "prelink" to avoid dirtying pages for shared libraries (reducing memory pressure) and see what it does for performance
* Running "prelink" to avoid dirtying pages for shared libraries (reducing memory pressure) and see what it does for performance
* Working on glibc and other popular libraries in the XO to reduce their dirty memory page footprint (it's huge and doesn't need to be)
* Working on glibc and other popular libraries in the XO to reduce their dirty memory page footprint (it's huge and doesn't need to be)

'''CPU cycle and process optimization''' <br>
* Fixing bug #4680 in PyGTK+, which causes every multithreaded Python GTK+ program to uselessly poll ten times a second.
* Fixing bug #4680 in PyGTK+, which causes every multithreaded Python GTK+ program to uselessly poll ten times a second.
* Replacing Sugar with Gnome, KDE, or other GUIs and seeing what it does for performance.


'''System level tests''' <br>
Suggestions from Erikg focused on Sugar optimization: <br>
* Replacing Sugar with Gnome, KDE, or other GUIs and seeing what it does for performance.
http://lists.laptop.org/pipermail/sugar/2008-October/009393.html
* Suggestions from Erikg focused on Sugar optimization: http://lists.laptop.org/pipermail/sugar/2008-October/009393.html <br>


'''Graphics performance''' <br>
Test results (thanks Neil!): <br>
Related thread: http://lists.laptop.org/pipermail/devel/2008-December/thread.html#22027 <br>
* Test results (thanks Neil!): <br>
Side by side Cairo graphics performance tests between a 2Ghz PC and XO <br>
Side by side Cairo graphics performance tests between a 2Ghz PC and XO <br>
http://screamingduck.com/Cruft/cairo_benchmark_XO.txt <br>
http://screamingduck.com/Cruft/cairo_benchmark_XO.txt <br>
http://screamingduck.com/Cruft/cairo_benchmark_2GHz_E2180.txt <br>
http://screamingduck.com/Cruft/cairo_benchmark_2GHz_E2180.txt <br>
http://screamingduck.com/Cruft/cairo_benchmark_XO_NoAccel.txt <br>
http://screamingduck.com/Cruft/cairo_benchmark_XO_NoAccel.txt <br>
* Tools: <br>

Tools: <br>
http://wiki.laptop.org/go/Performance_tuning
http://wiki.laptop.org/go/Performance_tuning



Revision as of 18:14, 31 December 2008

Feature subcategory Is part of::Category:Performance
Requesters {{#arraymap:Uruguay, Peru|,|x|Requested by::x}}
Requirements * For all of the following, the times measured should apply when the XO is connected to a wireless AP and running Write with a file of less than 1 MB. This is used as a sample "state of the machine" definition. Other definitions of state of the machine are welcome and the performance when the XO is doing more (e.g. more activities open or moving data over the Wireless) should not degrade precipitously.
  • The time between when the user interacts (e.g. clicks or enters a key stroke) when the result is visible on the screen should be less than 100ms. Specific cases are listed below and when the absolute number above is not achievable, a target percentage improvement is listed.
  • The following are examples where think release 8.2 does not meet this requirement.
  • Must be 80% faster than in 8.2 to show or hide the Frame.
  • Must begin showing scroll operation results in the Journal 50% faster than we do now. That is from the time I click on the scroll bar until the image on the screen starts to move.
  • Must copy and paste to the clipboard and show the clipboard icon in the Frame with the right type (text or image) of object 75% faster.
  • Must open a Journal detail page 50% faster.
  • Must show all icons when switching from one view to another (e.g. from Home to Neighborhood etc) 75% faster.
Specification See previous threads on this here:

http://lists.laptop.org/pipermail/sugar/2008-July/007471.html

Thread on SVG graphics performance here:
http://lists.sugarlabs.org/archive/sugar-devel/2008-December/010200.html

Suggestions from John Gilmore (e-mail here: http://lists.laptop.org/pipermail/devel/2008-December/021595.html)
File read write performance

  • Putting a swap partition on an SD card and seeing what it does for performance
  • Building an un-compressed JFFS2 filesystem (it's trivial with the tools used) and seeing what it does for performance

System memory usage optimization

  • Running "prelink" to avoid dirtying pages for shared libraries (reducing memory pressure) and see what it does for performance
  • Working on glibc and other popular libraries in the XO to reduce their dirty memory page footprint (it's huge and doesn't need to be)

CPU cycle and process optimization

  • Fixing bug #4680 in PyGTK+, which causes every multithreaded Python GTK+ program to uselessly poll ten times a second.

System level tests

Graphics performance
Related thread: http://lists.laptop.org/pipermail/devel/2008-December/thread.html#22027

  • Test results (thanks Neil!):

Side by side Cairo graphics performance tests between a 2Ghz PC and XO
http://screamingduck.com/Cruft/cairo_benchmark_XO.txt
http://screamingduck.com/Cruft/cairo_benchmark_2GHz_E2180.txt
http://screamingduck.com/Cruft/cairo_benchmark_XO_NoAccel.txt

  • Tools:

http://wiki.laptop.org/go/Performance_tuning

Owners {{#arraymap:MarcoPesentiGritti, Erik|,|x|Contact person::User:x}}
Priority Priority::2
Helps deployability? Helps deployability::no
Target for 9.1? Target for 9.1::no