Idle CPU usage regression

[kerams]

Describe the bug

Upgrading from 2024.3.11500-pre to 2025.1.13371-pre I see a significant increase in idle (even when there is no browser connection to Seq, and although events are being ingested constantly, it's usually far below 60/minute) CPU usage. Averages go up by several percentage points, and docker stats shows constant ~7% with spikes to 80% every 10 seconds or so. I have a diagnostic log ready should it be helpful.

To Reproduce

¯\_(ツ)_/¯

Expected behavior

CPU usage close to what it used to be before.

Screenshots

Environment (please complete the following information):

• OS: Ubuntu 22.04.5 arm64
• Browser [e.g. Chrome, Safari, Firefox, Edge]
• Seq Version 2025.1.13371-pre
• Using Docker? Yes

[liammclennan]

Hi @kerams

Thanks for the report. Idle CPU usage isn't necessarily bad, if it is doing indexing, or retention etc, but we will take a look to understand what has caused the difference.

[kerams]

I understand. It's a small instance though, so there shouldn't be much maintenance work to do all the time.

[liammclennan]

What hardware are you using for this instance?

[kerams]

A 4 arm64 core, 8GB VPS. Obviously, if this increase between versions is expected, I can live with it, but it looks suspicious.

[KodrAus]

It’s definitely something we’ll investigate before we stabilize this release. I’m actually just looking at one potential CPU abuse issue right now.

Thanks for the report! It’s very helpful to hear, ao if you spot anything else please don’t hesitate to raise more tickets.

[kerams]

Upgraded to 2025.1.13544-pre yesterday. Definitely an improvement - I hope it's not just the machine acting up randomly.

[nblumhardt]

Looks like the fix we made was the right one 👍

Thanks for keeping us in the loop, I'll close this as resolved but if CPU springs back up, let us know and we'll dig in further.