Progress in settings: Reduce update interval of remaining time

[MorrisJobke]

There is no need to update the remaining time 10 times per second (or even much), because you cannot read it then, because it alwas changes. 2 update sper second should be fully enough.

cc @guruz

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9951036-progress-in-settings-reduce-update-interval-of-remaining-time?utm_campaign=plugin&utm_content=tracker%2F216457&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F216457&utm_medium=issues&utm_source=github).

[guruz]

This (maybe) took a big amount of CPU on @nickvergessen 's machine.

[ckamm]

Note that my refactoring in #2328 already introduces a 1s timer for updating the estimates. I don't think it changes the mechanism with which the estimates are pushed to the ui though, so it'll likely still happen with each transmissionProgress() emission - too often.

[ckamm]

I'll check if I can do this for 1.8.1 in a way that doesn't gratuitously conflict with the refactoring.

[ckamm]

I did the change in ffd6c62, but at least on linux not many progress updates get skipped.

[ckamm]

I'm not happy with this kind of fix, since it may skip interesting updates. There's also a second slot connected to the progress info update that'd need throttling. We also fixed other bugs that had a much stronger performance impact. We'll revisit this once progress reporting has been further overhauled.

[ogoffart]

Closing old issue.
The progress impl has changed a bit since that time, and nobody is complaining anymore it is too frequent.