#5228: launching activities is slow
---------------------+------------------------------------------------------
Reporter: tomeu | Owner: tomeu
Type: defect | Status: new
Priority: high | Milestone: Retriage, Please!
Component: sugar | Version:
Resolution: | Keywords: performance
Verified: 0 | Blocking:
Blockedby: |
---------------------+------------------------------------------------------
Comment(by bernie):
Replying to [comment:23 tomeu]:
> So I think that points to the module level code as the reason why
importing modules is slow, not the reading and parsing of the modules.
I thought we had made it clear long time ago that activity startup time is
definitely not dominated by I/O, syscalls or .pyc parsing time (as many
claimed).
The bigger offenders, pygtk and the telepathy bindings, just do way too
much initialization work at import time, such as connecting to X11 and
dbus, instantiating lots of wrappers, etc.
But while we can't possibly rewrite all the poorly designed bindings out
there, we can at least push them in places where they aren't imported
unless strictly needed.
--
Ticket URL: <http://dev.laptop.org/ticket/5228#comment:24>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system