** Description changed: + [Test Case] + Performance fix - only way of testing i performing the benchmarking steps again to check if there is improvement. + + [Regression Potential] + No obvious regression potential. + + Original description: + I've been running a callgrind session trying to figure out how we could speed up opening the dash and it turned out that especially the first time the dash is opened, we spend more than 25% of time in QueueDraw - see the attached callgrind profile (best viewed with kcachegrind). Attaching also a simple unity patch that was used to collect the data + the command line was `valgrind --tool=callgrind --instr-atstart=no --collect-atstart=no compiz --replace ccp`.
** Description changed: [Test Case] - Performance fix - only way of testing i performing the benchmarking steps again to check if there is improvement. + Performance fix - only way of testing is performing the benchmarking steps again to check if there is improvement. [Regression Potential] No obvious regression potential. Original description: I've been running a callgrind session trying to figure out how we could speed up opening the dash and it turned out that especially the first time the dash is opened, we spend more than 25% of time in QueueDraw - see the attached callgrind profile (best viewed with kcachegrind). Attaching also a simple unity patch that was used to collect the data + the command line was `valgrind --tool=callgrind --instr-atstart=no --collect-atstart=no compiz --replace ccp`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994884 Title: QueueDraw is very expensive To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/994884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
