647
edits
Changes
Jump to navigation
Jump to search
Line 34:
Line 34: + + + + + + + + + + + + + + + +
Development Team/Prerequisites (view source)
Revision as of 09:39, 26 October 2009
, 09:39, 26 October 2009→Resources
==== Memory ====
==== Memory ====
Sugar on Fedora can run on 128MB of virtual memory with a reduced number of concurrent activities. The required amount of memory can be reduced by:
- streamlining the rest of the platform (e.g. use OpenEmbedded),
- substitute static bindings with ones generated at runtime (work ongoing upstream),
- optimization in Python,
- optimization in Sugar,
- forking all python processes from the same process (pre-forking).
==== General processing ====
==== General processing ====
Only shell and activities startup is dominated by non-graphics CPU power. A Geode LX 700 is acceptable. By using dynamic bindings instead of pregenerated ones, this limit can be lowered.
==== Graphics processing ====
==== Graphics processing ====
Sugar uses scaled graphics in all its UI. A system that is able to render an animation at fullscreen using Cairo at 12 fps will give a smooth user experience. If the system is not able to sustain that, memory can be traded for performance using the X11 composition extension or profiling work can happen at the librsvg, cairo and X driver levels.
==== Persistent storage ====
==== Persistent storage ====