Ticket #5470 (new defect)

Opened 7 years ago

Last modified 6 years ago

importing telepathy is slow

Reported by: tomeu Owned by: Collabora
Priority: normal Milestone: Opportunity
Component: telepathy-other Version:
Keywords: 8.2.0:- 9.1.0:? Cc:
Action Needed: diagnose Verified: no
Deployments affected: Blocked By:


Takes 12.5% of the total startup time of a minimal activity. See #5228 for more details and a profile.

Perhaps we should discuss it for update.1, as could be low hanging fruit that could help significantly activity startup.


imports3.log (4.4 kB) - added by tomeu 7 years ago.

Change History

Changed 7 years ago by jg

  • keywords update.1? removed
  • milestone changed from Never Assigned to Update.1

Changed 7 years ago by gdesmott

  • cc gdesmott added

Changed 7 years ago by morgs

  • cc morgs added

Changed 7 years ago by smcv

  • cc olpc@… added; gdesmott, morgs removed
  • owner changed from smcv to morgs

Reassigning to morgs, Cc the Collabora OLPC team, since I'm not currently working on OLPC.

Changed 7 years ago by mtd

takes 13 seconds to import telepathy (see [#5228 comment]) in update.1 690.

Changed 7 years ago by mtd

1.3 seconds, sorry.

Changed 7 years ago by morgs

  • cc olpc@… removed
  • owner changed from morgs to Collabora

Changed 7 years ago by tomeu

Take in account that these 1.3 seconds is not what it takes to an activity to import telepathy, as it includes the import of several modules that need to be imported anyway.

So, the right way of calculating the impact of one import is to see which other modules it imports and subtract the time taken by those modules that need to be imported from other parts of the activity.

Attached is a file with all the modules imported by a very simple activity, taken with 'python -v sugar-launch <activity name>'.

If we wanted to know how much impact has the telepathy module in activity startup, we would need to move the imports caused by 'import telepathy' to the end, and time those.

Changed 7 years ago by tomeu

Changed 6 years ago by mstone

  • keywords 8.2.0:- 9.1.0:? added
  • next_action set to diagnose
  • milestone changed from 8.2.0 (was Update.2) to Opportunity

This is does not need to be fixed in 8.2.0 because the the rainbow module importing hack masks the performance problem.

Note: See TracTickets for help on using tickets.