Cairn
NousResearch/hermes-agent

Dashboard session stats SQL aggregation performance fix

Cluster 48914 · dashboard. Data as of

Nothing open on GitHub. Fix merged in #73362. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #73362. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #73362. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items all concern the same inefficiency in /api/sessions/stats, which fetches large numbers of full session rows instead of using a SQL GROUP BY to aggregate counts by source. The proposed fix replaces an O(N) approach with a single aggregating query.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #73362 perf(dashboard): use GROUP BY for session stats instead of fetching 10k rows

    merged to main

    files: hermes_cli/web_server.py, hermes_state.py, tests/hermes_cli/test_dashboard_admin_endpoints.py, tests/test_hermes_state.py

3 PRs closed without merging

From the close comments: duplicate 1 · merged via another change 1 · superseded by another PR 1

  • #48921 perf(dashboard): use GROUP BY for session stats instead of fetching 10k rows · merged via another change → #73362
  • #48932 perf(dashboard): replace O(N) session_count() loop with single GROUP BY query in /api/sessions/stats · superseded by another PR → #48921, #48914
  • #61120 perf(dashboard): aggregate session stats by source in SQL · duplicate → #48921
Closed issues · 1
  • Closed#48914perf(dashboard): /api/sessions/stats fetches 10 000 full session rows to count by source -- O(N) to O(1) fix available
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
dashboard
Merged PRs
#73362
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
28 Jul 2026

For your agent

The same facts, typed.

cluster/48914.json
cluster/48914.md