-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jameson "Chema" Quinn wrote: | One low-hanging fruit for faster activity start is having activity install | compile .pyc files, with (tiny) extra points if the .pyc gets hints to not | use jffs2 compression. This is on my gameplan with the bundle format update | stuff, but I have gotten stuck on the signatures (openssl cannot read ssh | public keys) so I am behind on that. I had hoped to finish it in my free | time this week but starting next week I cannot be so sure I'll have time.
Pretty small fruit. Based on my measurements (http://lists.laptop.org/pipermail/sugar/2008-March/004669.html), we are talking about less than 200 ms for typical Activities. The only Activities I know of with enough code for this to matter are the TamTam activities. Even the Journal spends much less than one second compiling. ~ Additionally, my measurements include the time to write the pyc file back into jffs2, so the real launch delay could be even less. - --Ben -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIK5JwUJT6e6HFtqQRAhbqAJ9jrt0gENi+ar1CCq0QU2O891SH7wCdFlsD JW1/uQlAarBii8WB7V4WVkA= =z9mP -----END PGP SIGNATURE----- _______________________________________________ Sugar mailing list [email protected] http://lists.laptop.org/listinfo/sugar
