© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
Thanks for the hints, that helped. Apparently deep nesting happens when patterns are shared between contexts. I'm not sure if this was a save thing to do at all. I've switched them to surfaces and now there are no high index values in the trace anymore.
I had hopes, but unfortunately this did nothing for the performance issue, it may even do slightly worse.
Bypassing the driver does make a difference, though:
$ ./onboard
draw 13635.882ms
$ GDK_RENDERING=image ./onboard
draw 1371.348ms
That number is the initial caching plus the first redraw. That's probably already good enough for the startup, but not yet for all later interaction. From there on python/python-gi show up as bottlenecks too.