On 2013-09-02, at 06:25, Stephan Eggermont <[email protected]> wrote:
> Stef wrote: >> did you notice a different between SystemAnnouncer and replacing it by >> another one? > > Yes, it made a significant difference. It did not remove enough overhead > though. > Job>value: was called over 100K times, doing that only every 100 increments > helped enough. the main problem with the current progress bar morph design is that updates are forced whenever the underlying model (here job) changes. This is *very* costly for high-frequency updates, which is exactly the moment when you want to use the progress bar ;) It should work the other way around, the progress bar morph polls the underlying model with a given frequency (~10/s) and then refreshes the UI if the model changed.
signature.asc
Description: Message signed with OpenPGP using GPGMail
