[bug] feed sync causing spike in FF's power usage

[ghost]

• FF 69 | 70 | 71
• Brief 2.6.0
• W10 Pro x_64 v1903 b18362.295

  ---

  Got around 90 feeds and when being synchronised FF's power usage in the OS's task manager is spiking to HIGH | VERY HIGH and also FF's own task manager is reporting the same spike in energy impact for Brief, which is not healthy for the performance of FF and the system overall.

The log is riddled with this sort of entries, if that is that cause:

possibly raw html in possibly raw html in <content type="xhtml" xml:base=

[tanriol]

@n8v8R, sorry for not getting back to you earlier.

There are a few possible causes, so, if you're still seeing this, it would be valuable to know whether that happens:

• with an open foreground Brief tab in some window, or
• with an open background Brief tab somewhere, or
• with no Brief tabs but with the unread items counter on the badge active, or
• with no Brief tabs and without unread counter on the Brief button?

There are some fixes queued for the first couple of scenarios, but not for the latter two (and the final one may be really hard to fix if the problem is the parsing itself).

[ghost]

if you're still seeing this

still exhibits, meantime on

• W10 Pro x_64 v1909 b18363.752
• FX 77 x_64

  ---

  • with an open foreground Brief tab in some window, or
  • with an open background Brief tab somewhere, or
  • with no Brief tabs but with the unread items counter on the badge active, or
  • with no Brief tabs and without unread counter on the Brief button?

Those high spikes (almost up-to 30 in the Energy Impact column) appear to only happen with the Brief tab open, independent of whether the tab being in foreground or background. If in foreground interaction (e.g. deleting feeds) with Brief becomes very sluggish during sync activity. With a closed tab the energy impact is definitely less during sync activity. Enabling/Disabling badge counter would appear not to change the outcome in any case.

[tanriol]

Those high spikes (almost up-to 30 in the Energy Impact column) appear to only happen with the Brief tab open, independent of whether the tab being in foreground or background.

Thank you, this sounds optimistic: the code in the Brief tab that works in background and can consume much CPU is the feedlist update code, which had a couple fixes recently in 81efdaf09cc9828c01e7164cf1a15d07285f05fa and 627f4e38e8acc30e48c38a630f11b57f6f85e0fd.

[ghost]

There seems some improvement - tested with Master - yet there are still some spikes occurring - see the screen capture screen cast.zip

Not sure, might be that checking some particular feeds is causing spikes whilst others may not