[Sugar-devel] A trick to profile activities startup time

[Gonzalo Odiard]

Actually, I find this last part was a mistake from my part,
because I was testing in 0.100 in the XO,
and the code is a little different than in master.

The line 375 is:

    def run_main_loop(self):
        Gtk.main()

then, need continue looking.

Gonzalo





On Thu, May 22, 2014 at 6:24 PM, James Cameron <quozl at laptop.org> wrote:

> On Thu, May 22, 2014 at 10:10:28AM -0300, Gonzalo Odiard wrote:
> > Now, almost all the time, is spent in:
> >
> >         1    4.278    4.278    6.741    6.741
> activity.py:375(run_main_loop)
> >
> > What is that?
> >
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/src/sugar3/activity
> > /activity.py#L375
> >
> >  _initialize_journal_object have a nice FIXME
> >
> >         # FIXME: We should be able to get an ID synchronously from the
> DS,
> >         # then call async the actual create.
> >         # http://bugs.sugarlabs.org/ticket/2169
> >
> >
> https://github.com/sugarlabs/sugar-toolkit-gtk3/blob/master/src/sugar3/activity
> > /activity.py#L425
> >
> > points to a bug 4 years old :(
> > (there are more information in this bug [2].... 7 years old!
>
> Nice find, well done.  I don't know of anybody else having done
> profiling like this for about four years, so you may find other ways
> to improve startup time.
>
> --
> James Cameron
> http://quozl.linux.org.au/
>



-- 
Gonzalo Odiard

SugarLabs - Software for children learning
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20140522/6acd2f9a/attachment.html>