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.
On Wed, May 14, 2008 at 6:57 AM, Marco Pesenti Gritti <[EMAIL PROTECTED]> wrote: > On Wed, May 14, 2008 at 1:46 PM, Mikus Grinbergs <[EMAIL PROTECTED]> wrote: > > > * More responsive UI - faster launch of activities > > > > > > Is the solution currently in joyride satisfactory for the August > release? > > > > I use a recent Joyride on my G1G1. My average time to launch Browse > > (from the time I click in the F3 Activity Ring on the Browse icon, > > to the time when I can click on the entry field in Browse itself (so > > that I can start typing in an URL) is 25 seconds. > > If you could download the latest joyride, time startup and open a > ticket that would be useful. 25 seconds are too much obviously. > > Please take both time on the very first start and after a reboot, > xulrunner does component registration on the very first start which > could be expensive > > Thanks. > Marco > _______________________________________________ > Sugar mailing list > [EMAIL PROTECTED] > http://lists.laptop.org/listinfo/sugar >
_______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
