Big Performance Issue - Hit Testing on Editor Activation [message #231424] |
Thu, 08 March 2007 17:02  |
Eclipse User |
|
|
|
I recently added several thousand connections to my diagram. I fixed
some scrolling problems, but now I am having a problem I don't think I
can fix. When selecting the diagram editor, it is taking around 5
seconds to become active. I profiled it and it seems that hit testing
(containsPoint()) is being done on _every_ edit part in the diagram and
this is what is consuming the time. I wanted to see if anyone else has
this problem and if there is something that can be done.
thanks,
adam
|
|
|
|
|
|
|
Re: Big Performance Issue - Hit Testing on Editor Activation [message #231618 is a reply to message #231544] |
Mon, 12 March 2007 17:22  |
Eclipse User |
|
|
|
thanks for the info, Randy. It's good to see you over here;)
Randy Hudson wrote:
> That code is known to have n^2 performance, unfortunately. A patch could
> probably improve it. You can also short circuit the whole focus search by
> setting the top figure as disabled or no focusable or something like that.
> That probably makes the most sense.
>
> "AdamC" <acabler@hotmail.com> wrote in message
> news:esq4dm$d63$1@utils.eclipse.org...
>> I did some more digging and it looks like all the time is being spent in
>> FocusTraverseManager.getNextFocusableFigure. This is making things
>> unusable for me atm. If anyone has some thoughts on this, I would
>> appreciate it.
>>
>> adam
>>
>> AdamC wrote:
>>> I recently added several thousand connections to my diagram. I fixed
>>> some scrolling problems, but now I am having a problem I don't think I
>>> can fix. When selecting the diagram editor, it is taking around 5
>>> seconds to become active. I profiled it and it seems that hit testing
>>> (containsPoint()) is being done on _every_ edit part in the diagram and
>>> this is what is consuming the time. I wanted to see if anyone else has
>>> this problem and if there is something that can be done.
>>>
>>> thanks,
>>> adam
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.07662 seconds