Comment 2 for bug 708388

On Thu, 2011-01-27 at 00:38 +0100, Krzysztof Kościuszkiewicz wrote:
> It seems the problem largely goes away when zoomed in/out.
> Actions take most time when "zoom extents" has been executed.
> This points to inefficient screen update.

It could be that computing the invalidated region for each individual
object is causing a slow-down.

Also possible (but I'd be surprised) is the possibility that we are
actually repainting after each individual selection.

Also possible - are text object bounds being invalidated, such that the
core has to re-query pango for text extents on each object?

For comparison - is there any difference in performance when dragging a
big box to select anything?

I think the next step for testing would be to code up a long loop to
repeatedly run the select / deselect action, then use a system profiler,
like sysprof to see just where the code is spending its time.