Doh! It wasn't the invoke. We had a late import on the gui thread which was
blocking, and the invoke was waiting for that to complete.
Sorry about the false alarm and thanks for all the help.
Glenn
___
Users mailing list
Users@lists.ironpython.com
http:
er 25, 2008 10:40 AM
To: Curt Hagenlocher
Cc: Discussion of IronPython
Subject: Re: [IronPython] Question about Control.Invoke and CallTargets
We only see the long pause in IP2. To give a feeling of magnitude:
* The first recalc of Resolver (without user input) takes ~3500ms, almost the
same as IP1
We only see the long pause in IP2. To give a feeling of magnitude:
* The first recalc of Resolver (without user input) takes ~3500ms, almost
the same as IP1
* The first recalc with user input that hits this issue takes ~5000ms
* Recalcs after that take ~400ms, which is on par with IP1
Interesting
Is this something that changed between 1.1 and 2.0 or do you see the same
behavior in both?
On Tue, Nov 25, 2008 at 7:47 AM, Glenn Jones
<[EMAIL PROTECTED]<[EMAIL PROTECTED]>
> wrote:
> Hello guys,
>
> We're seeing some strange behaviour when doing cross-thread invoking in
> Resolver. Unfortunate
Hello guys,
We're seeing some strange behaviour when doing cross-thread invoking in
Resolver. Unfortunately, we can't get a minimal repro for this, so I'll just
describe what's going on and hopefully something will be obvious.
We do our recalcs in a background thread, to avoid blocking the GUI. W
