[QUESTION] Am I the only experiencing slow response times?

[nikolajfleischer]

Which component is your question about?

Lite

Performance Monitor Version

2.10.0

Is your question about how it works, or the results?

How the tool works

What's your question?

If connected to a server and I want to return to the general overview, I will get the spinning wheel. Also clicking through the different menu items when connected to a server, it may not give the spinning wheel, but there will be a 2-3 seconds delay from clicking until the new item is loaded. For instance going from Blocking - Trends --> Blocked Process Reports.
It may be connected to the compacting of the database, as I have noticed this when it especially bad, that it says compacting.
I had upwards of 16-17 servers and it helped to scale back to around 8.

Probably should have a different issue regarding other "issues", but here goes:

• In the FinOps, licensing (Enterprise edition is mentioned even when connected to a read only AG.
• On this version I previously had the same alerts pop up several times, hours after it happened.
• Have noticed CPU usage in the 25-27 % range and at the same time memory of 3.5 GB

Additional Context

No response

[erikdarlingdata]

Thanks for the detailed report, @nikolajfleischer — and good instinct splitting it up. You're not the only one, and your diagnosis was on the right track. Here's what's going on with each part:

1. Spinning wheel / 2–3 s delays when navigating — this is the archival/compaction, exactly as you suspected. Lite serialises database access with a reader/writer lock: the UI takes a read lock for every tab, and archival takes an exclusive write lock. Today archival holds that write lock across the entire export-to-Parquet step, and a tab switch blocks until it finishes. More servers → more data to export → longer freeze, which is why scaling from ~16 to ~8 helped. Tracked in #979, and it's being worked on now — the export doesn't actually need the exclusive lock, so this is fixable.

2. FinOps shows "Enterprise" on a read-only AG secondary — SERVERPROPERTY('Edition') returns the licensing edition regardless of replica role, and FinOps doesn't currently detect that it's connected to a readable secondary. Tracked in #980.

3. Same alerts re-firing hours later — the alert cooldown that prevents duplicates is held in memory only, so an app restart wipes it and recently-fired alerts can fire again. Tracked in #981.

4. CPU 25–27% / 3.5 GB RAM — with 16–17 servers this is expected: Lite keeps a working set sized for the compaction step, and that many servers is past what a single Lite instance is sized for. Scaling back to ~8, as you found, is the right move.

One concrete recommendation: you're on 2.10.0 — please upgrade to the latest release. 2.11.0 includes compaction memory/throughput tuning that helps #1 and #4, plus alerting fixes relevant to #3. The archival write-lock fix in #979 will follow in a later release.

Closing this question issue since the actionable items are now tracked in #979 / #980 / #981 — follow those for progress.

[nikolajfleischer]

Thank you for the quick response!

Caught this to document it:

Currently unable to update, as server is busy with other tasks, for the next week or so. Nothing too resource intensive, just cannot break the workflow with reboot, due to .Net upgrade.

Sorry if this comment reopens the issue, will try and close it afterwards.