Skip to content

perf(sidebar): mount only the session rows near the viewport - #15090

Merged
bolichen97 merged 1 commit into
kirodotdev:mainfrom
Pearcekieser:perf/sidebar-virtual-sessions
Sep 30, 2026
Merged

bolichen97 merged 1 commit into
kirodotdev:mainfrom
Pearcekieser:perf/sidebar-virtual-sessions

Conversation

@Pearcekieser

@Pearcekieser Pearcekieser commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: the Sessions sidebar stays responsive with hundreds of sessions.

With a few hundred sessions, switching sessions, typing in the sidebar search and even leaving the dashboard idle produce long main-thread tasks. Issue #15088 has the measurements: five session switches cost 18 s of long tasks at 600 rows against 2.4 s at 50.

Why it matters

Heavy users keep hundreds of live sessions, and the sidebar is on screen for every chat. Every switch, keystroke and status tick pays a cost that grows with the whole list, so the dashboard gets slower the more it is used.

Not a goal

  • Replacing the lanes with a list virtualizer (react-virtuoso) that owns the DOM. The tree, drag and drop, sticky folder headers and the DOM-reading features stay as they are.
  • Making a single row cheaper. The per-row hooks, menus and drag handles are unchanged.
  • The Older Sessions history pane, which renders its own rows.

What changed (motivation → approach → change)

The sidebar's cost follows the number of mounted rows, not the visible ones. Rendering only the first 40 rows of a 600-session list brought every measurement back to the 50-row level. content-visibility: auto already skips paint for off-screen rows, but not their React, subscription, dnd-kit and Framer work.

A row far from its lane's viewport now renders as a stub instead. The stub has the same height, shows the title on the row's second line in the row's own text color (the session key for an untitled session, as the real row does), and carries the same data-slot-key, data-session-row, scope and container attributes, so keyboard navigation, digit shortcuts, hover hold, scroll memory, reveal and anything else that looks rows up still find every row in order. One IntersectionObserver per lane scroller, with a 1200px margin, mounts the real row before it scrolls into view and stubs it again once it is that far out. A general virtualizer was rejected because it needs one flat item list and takes over the DOM, which the folder tree and those features depend on.

Piece What it does
pages/chat/sessionRowWindow.tsx the observer, the height cache, the stub, and each root's first-paint budget (48 rows); WindowedSessionRow renders the row unchanged with no wrapper when there is no observer
renderSessionRow in pages/ChatSidebar.tsx wraps every row; the active, renaming, dragged and revealed rows never stub
lane scrollers in pages/ChatSidebar.tsx the tree, flat and conductor lanes and each board column are an observer root, so each column mounts its own first rows

A row that holds focus or an open menu is not stubbed while it does, and is stubbed once the focus leaves or the menu closes if it is still out of the window, and a zero-height report from a row inside a collapsed folder leaves the row as it was. A stub is a Tab stop like the real row. Focusing, clicking, middle-clicking, right-clicking or pressing Enter or Space on a stub mounts the real row and hands that focus or event to it, so the real row's own handlers, including its context menu, decide what happens. The unmeasured stub height is 76px, the size a never-painted .session-row already takes, so the lane's scroll height is unchanged. docs/feature-map/README.md lists the new file under Sessions.

Backwards compatibility

Compatible: no API, setting or stored state changes. Without IntersectionObserver the sidebar renders exactly as on main.

Tests

  • src/test/sessionRowWindow.test.tsx: no observer means no wrapper; one observer rooted on the lane; stubs keep row identity (data-slot-key, data-session-row, title) and DOM order and mount when near; stub height is the last real height, and a zero-height "not intersecting" report changes nothing; each root mounts its own first rows, including under StrictMode; keepMounted, focus and an open menu keep the row live; focusing a stub moves focus onto the mounted row; the stub is a Tab stop; a click, a modified click, a middle-click, a right-click and Enter/Space on a stub reach the real row once, including the real press-then-click sequence where the press must not swap the stub out; a late root does not remount rows; a row held by focus or an open menu stubs once released.
  • src/test/ChatSidebar.rowWindow.test.tsx also pins that a stub carries the same data-session-* attributes, role and tab stop as a real row, inside a [data-slot-key] box with the same key.
  • src/test/ChatSidebar.rowWindow.test.tsx: through the real sidebar, rows past the window are stubs in order, the lane scroller is the observer root, the active row stays mounted past the window, and a row the observer reports near mounts. All four fail on main.
  • Existing ChatSidebar, ChatPage and SessionFlyout suites (174 files) pass unchanged; the shared test IntersectionObserver in integration/setup.ts means they run with the window active.

Manual verification

Production build, stubbed API, Playwright Chromium, 4x CPU throttle, total long-task time:

Action 300 rows, main 300 rows, this PR 600 rows, main 600 rows, this PR
5 session switches 7.8 s 3.0 s 17.7 s 3.3 s
Typing 7 characters in search 2.2 s 0.7 s 4.3 s 0.9 s
3 s idle 1.1 s 0.15 s 3.2 s 0.18 s
Initial load 7.9 s 4.9 s 10.1 s 5.1 s
Scrolling 8000px in 20 steps 0 s 0.17 s 0.1 s 1.0 s

Scrolling now pays for the rows it brings in; no single task exceeded 71 ms. After a jump past the window, stubs stay in view for 200 to 310 ms at 4x throttle and 330 to 580 ms at 6x before the real rows replace them. A click on a stub in that gap opens its session in Chromium, and a right-click opens its session menu, the same as on a mounted row. A drag from the last row that autoscrolls up past about 100 stubbed rows still drops onto a folder header: stubs are never drop targets, and folder headers and the root group are never stubbed. With 600 sessions in 20 folders, five switches went from 23.5 s to 3.9 s. On a 400-session lane, scroll height and the row at a given scroll position match main (30287px, row 163 at the same offset after settling). DOM nodes at 600 rows fell from 15,803 to 2,593.

Screenshots / video

At rest the lane looks the same. Both shots show the same 400-session list at the same scroll position, 60% down the lane.

Before (main):

Sessions lane on main, scrolled 60% down

After (this PR):

Sessions lane with row windowing at the same position

A stub is visible only in the frame after a jump the window has not caught up with, such as dragging the scrollbar thumb to the end. The first shot is that frame, taken with the observer held back so it stays on screen. The second is the same position once the observer runs, and every row is real again.

Jump frame: stubs showing titles only, before the observer mounts the rows

The same position settled: every row mounted

Drag across the stubbed rows

A session dragged from the bottom of the lane autoscrolls up through about 100 stubbed rows and lands on the Project A folder header. The folder move request (PATCH /api/chat/slots/chat-395/folder with folder_id: f0) was sent.

Dragging session 395 over the Project A folder header after autoscrolling past stubbed rows

Related Issues

Fixes #15088

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@Pearcekieser
Pearcekieser requested a review from a team September 29, 2026 18:38
@Pearcekieser
Pearcekieser requested a review from a team as a code owner September 29, 2026 18:38
@Pearcekieser

Copy link
Copy Markdown
Contributor Author

Intent: keep the Sessions sidebar responsive with hundreds of sessions by mounting only the rows near each lane's viewport, while every feature that walks rows in DOM order keeps working.
Not a goal: replacing the lanes with a DOM-owning list virtualizer, making an individual row cheaper, or changing the Older Sessions history pane.

@github-actions github-actions Bot added readiness: checking Automated validation is still running fork Pull request from a fork (external contributor) labels Sep 29, 2026
@github-actions

github-actions Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Fable 5, fork) — ✅ PASS

Design-level review of dc57565e23af0f8f9f00de078167ff8695bd8984 via the fork AI-review pipeline — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Verify a drag gesture begun on a still-visible stub (in the post-jump gap) fails gracefully — stubs swallow mousedown, so the lift silently no-ops until the row mounts.

[DESIGN-REVIEWED] dc57565

Description read

[DESCRIPTION-READ] 00b8b91e087cf8cb6ff2360ac8d58a110a6d2fd9c805ce64c2b78eff59e2632a

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Fable 5, fork) — ✅ PASS

Premise-level review of dc57565e23af0f8f9f00de078167ff8695bd8984 via the fork AI-review pipeline — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

First-Principles-Verdict: PASS

Verify stub activation (click/focus replay after mount) on a non-Chromium engine — manual verification ran Playwright Chromium only, and the mousedown-prevent/replay sequence is engine-sensitive.

What this change ships

Inventory (10 items) — 9 justified

Intent: keep the Sessions sidebar responsive with hundreds of sessions — a FIX (perf defect, issue #15088 with linked measurements; four new wiring tests fail on base). The existing virtualizer (react-virtuoso, pages/LogsPage.tsx, counted: 1 production consumer) was considered and rejected for a derived reason — the lanes' DOM-order features and nested tree; content-visibility: auto on .session-row (index.css:2557, verified) already covers paint but not React work.

  1. Rows far from a lane's viewport render as same-height stubs, so sidebar cost stops growing with list size — justified
  2. Stubs are briefly visible after a fast scroll jump until real rows mount — justified
  3. Clicking, middle/right-clicking, focusing or keying a stub mounts the real row and hands it the event — justified
  4. Active, renaming, dragged, revealed, focused and open-menu rows never stub — justified
  5. First 48 rows of each scroller render real at first paint — justified
  6. Each board column windows independently as its own observer root — justified
  7. Without IntersectionObserver the sidebar renders exactly as on main — justified
  8. Feature-map README gains the new file's line — justified
  9. Five screenshots committed under temp-screenshots/sidebar-row-window/ — rides along (repo convention; 30+ sibling directories exist)
  10. Test-only height-cache reset hook and exported tuning constants — justified

[FIRST-PRINCIPLES-REVIEWED] dc57565

Description read

[DESCRIPTION-READ] f8366a2f23bb802a695a6300237da71533f1702f83d614156abef9eb347393e5

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Fable 5, fork) — 🟡 CONCERNS

UX-level review of dc57565e23af0f8f9f00de078167ff8695bd8984 via the fork AI-review pipeline — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

UX-Verdict: CONCERNS

No blind reader has cold-read the new stub rows; all states are shown in committed screenshots, but comprehension of the placeholder frame is unverified in this fork lane.

Watch

  • Stub rows render title only (<div className="truncate">{title}</div> after a blank meta line) — after a scrollbar jump the lane shows rows stripped of timestamps, running/"Thinking…" and unread signals for the 200–580 ms the author measured (longer on weaker hardware), so a user scanning for "which session needs me" briefly sees a status-less list (after-jump-frame.png). Rare trigger, transient, self-heals; a human should confirm the settled screenshot's recovery matches real hardware. No code change asked — verify only.

Suggestions

  • The stub sets a native title={title} tooltip the real SessionRow does not carry; drop it (the visible truncated text plus the accessible name suffice) so hover behavior doesn't differ between the two frames of one row.

[UX-REVIEWED] dc57565

Description read

[DESCRIPTION-READ] 064785a73dbb974ee8e20d8b154704b6e579fd765237dfaaaf9bb3790410d72b

That sha256 names everything this verdict read: the PR description, plus the 8 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

GPT 5.6 Review (fork) — ✅ no blocking findings

Reviewed dc57565e23af0f8f9f00de078167ff8695bd8984 via the fork AI-review pipeline; updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] dc57565

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Sep 29, 2026
@github-actions

github-actions Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5 Review (fork) — ✅ no blocking findings

Reviewed dc57565e23af0f8f9f00de078167ff8695bd8984 via the fork AI-review pipeline; updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] dc57565

@Pearcekieser
Pearcekieser force-pushed the perf/sidebar-virtual-sessions branch from bad5902 to 1b05dad Compare September 29, 2026 20:21
@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • Cannot evaluate: rendered evidence missing

fixed in 1b05dad: the description's images were fork blob URLs the pipeline could not download.
The five screenshots are now committed at the head under temp-screenshots/sidebar-row-window/ and referenced by repository path.
They cover the lane at rest before and after, the jump frame with stubs in view, the same position settled, and a drag across stubbed rows.

@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • Watch: drag past the mounted window

fixed in 1b05dad (verified, no code change needed): a drag from the last row autoscrolled up through about 100 stubbed rows and dropped on the Project A folder header; the PATCH /api/chat/slots/chat-395/folder request carried folder_id f0.
Stubs were never drop targets: session drops land on folder headers and the root group, which are not windowed, and the dragged row itself is kept mounted (keepMounted on activeDrag).
Evidence: temp-screenshots/sidebar-row-window/after-drag-over-folder.png, described under Manual verification.

@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • Watch: stub shows a bare title during a jump

rebutted: the stub is visible only in the frames between a jump past the 1200px window margin (scrollbar-thumb drag, End) and the observer's next delivery; ordinary wheel and keyboard scrolling stays inside the margin.
The jump-frame and settled screenshots (temp-screenshots/sidebar-row-window/after-jump-frame.png, after-jump-settled.png) show the flash reads as rows still loading, then every row real, with running and unread state restored.
Carrying unread, running, pin and colour into the stub would mean the store subscriptions whose per-row cost this PR removes.

@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • Suggestion: drop text-muted from the stub

fixed in 1b05dad: the stub title now uses the row's own text color, so a stub caught in view reads as the same row not yet loaded.

@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • Stub drops the untitled-session fallback

fixed in 1b05dad: renderSessionRow passes s.title && s.title !== s.key ? s.title : s.key, the fallback the other row renderers use, and the stub carries it as its title attribute, so an untitled slot's stub shows and names its key.

@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • Initial-mount budget is lane-wide, not per window root

fixed in 1b05dad: the initiallyMounted prop is gone; each window root (the lane, or one board column) hands its own rows a first-paint budget of 48 through claimInitialMount, reset on each render of the root and keyed by row so a StrictMode double initializer does not spend two positions.
Tests pin two roots mounting their own first rows, the default budget, StrictMode, and a fresh budget per render pass.

@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • Zero-height entry still flips the row to a stub

fixed in 1b05dad: a zero-height "not intersecting" entry (a row inside a collapsed folder) now returns before the near decision, so the row keeps whatever state it had until the folder opens and a real entry arrives.
A zero-height "intersecting" entry still mounts: an unlaid-out box may be on screen and a spare mount is the cheap mistake; the shared test IntersectionObserver in integration/setup.ts reports rows that way.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Sep 29, 2026
@Pearcekieser
Pearcekieser force-pushed the perf/sidebar-virtual-sessions branch from 1b05dad to 4989336 Compare September 29, 2026 21:52
@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • Stubbed session rows cannot be activated

fixed in 4989336: the stub cancels mousedown (so the press does not move focus and swap the stub out before click), records click, auxclick and Enter/Space, mounts the real row, then focuses it and replays the event on it, so SessionRow's own onClick / onAuxClick / onKeyDown decide the outcome.
Verified in Chromium against the built SPA with the observer held back: clicking a stub opens its session (/chat/session-1, row active), the same as the mounted-row control.
Regression tests in sessionRowWindow.test.tsx cover click with modifiers, middle-click, Enter/Space, and the press-then-click sequence.

@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • Duplicate 48-row constant

fixed in 4989336: the two are independent, and the comment now says so. SESSION_ROW_INITIAL_MOUNT_BUDGET is how many rows each window root mounts on first paint; SIDEBAR_DISPLACEMENT_WINDOW bounds which rows animate on a reorder. Either can change without the other; the "change together" claim is gone.

@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • A click during the stub frame does nothing

fixed in 4989336: same defect as the GPT finding. The stub keeps its box through the press, then forwards the click, middle-click or Enter/Space to the real row once it mounts. A Chromium click on a visible stub opens its session.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Sep 30, 2026
@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • Stub title inset differs from the real row by a few pixels

rebutted as disproportional for this head: the offset is 4px (5px inside a folder) and exists only while a stub is on screen, 200 to 580 ms after a jump past the 1200px margin; nothing is mis-clicked or mis-read.
The suggested fix is not free: putting the session-row class on the stub pulls in content-visibility and contain-intrinsic-size from index.css, which changes the stub's measured height and the lane geometry this PR keeps equal to main, and the row-count tests that key on .session-row.
Aligning the padding with ROW_BOX_CLS alone is a safe one-line follow-up and will be folded into the next push if this PR needs one.

@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • Suggestion: pin the 76px stub default to contain-intrinsic-size with a test

rebutted as disproportional: jsdom does not load index.css, so the test would have to parse the stylesheet text; the pairing is documented at both ends (SESSION_ROW_STUB_DEFAULT_PX and useLaneScrollMemory) and the geometry was measured equal to main in Chromium (30143 vs 30131px on 400 rows).
A drift shows up as scroll-position shift in the committed jump screenshots rather than silently.

@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • Suggestion: wiring test should assert SESSION_ROW_INITIAL_MOUNT_BUDGET

accepted, not changed on this head: both constants are 48 today, so the test is correct now but would fail for the wrong reason if only one changed. The one-line swap will be folded into the next push if this PR needs one, rather than restarting the full CI round for a test-name change.

@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • Watch: running, unread and time cues vanish during the catch-up

rebutted: this is the stub's purpose. Carrying running/unread/time into the stub needs the per-row store subscriptions this PR removes, which is the cost it exists to cut. The window is 200 to 580 ms after a jump past the 1200px margin (measured); ordinary scrolling never shows a stub, and every cue is back once the row mounts (after-jump-settled.png).

@Pearcekieser

Copy link
Copy Markdown
Contributor Author
  • Watch: untitled sessions stub with their key

acknowledged, no change: the stub uses the same fallback the real row renders (s.title || s.key), so the text the user sees does not change when the row mounts; slot keys are short chat-* identifiers, the same text an untitled row already shows today.

@Pearcekieser

Copy link
Copy Markdown
Contributor Author

@kirodotdev maintainers: PR Readiness on e29b33a is stuck on its 02:05 UTC evaluation ("waiting on Opus 5 Review (not started)"), but the Opus 5 Review check-run completed with success at 02:15 UTC and every other check on this head is green; every review item has a disposition above. The self-heal sweep has not recomputed it in 35 minutes, and a fork contributor cannot dispatch the workflow. Could one of you recompute it?

gh workflow run pr-readiness.yml -f pr=15090 -f sha=e29b33a77b9e1422ca5b89f18fbceb55e85515eb

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: checking Automated validation is still running labels Sep 30, 2026
Every session row carries a query observer, several store subscriptions, a
dnd-kit draggable and droppable, a Framer node and two Radix menus, so the
sidebar's cost grew with the number of mounted rows. With a few hundred
sessions a switch, a search keystroke and even an idle tick turned into
multi-hundred-millisecond long tasks.

Rows far from their lane's viewport now render as a stub of the same height
that keeps the row's data-session-row, scope and container attributes, and
mount the real row when an IntersectionObserver rooted on the lane scroller
brings them within 1200px. The active, renaming, dragged and revealed rows
never stub; a row holding focus or an open menu is not unmounted. Without
IntersectionObserver rows render exactly as before, with no wrapper.
@Pearcekieser
Pearcekieser force-pushed the perf/sidebar-virtual-sessions branch from e29b33a to dc57565 Compare September 30, 2026 05:17
@Pearcekieser

Copy link
Copy Markdown
Contributor Author

Rebased onto main after #15094 split ChatSidebar into pages/chat-sidebar/*: the same row-windowing wiring re-applied, no behaviour change; windowing and sidebar tests, tsc and a Chromium check re-run green.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running and removed readiness: passed Eligible automated validation passed for the current revision merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: action required A blocking check or review needs attention labels Sep 30, 2026
@Pearcekieser

Copy link
Copy Markdown
Contributor Author

@kirodotdev maintainers: PR Readiness on dc57565 is stuck on its 05:50 UTC evaluation ("waiting on Opus 5 Review (not started)"), but the Opus 5 Review check-run completed with success after it and every other check on this head is green; every review item has a disposition above. The self-heal sweep has not recomputed it in 40 minutes, and a fork contributor cannot dispatch the workflow. Could one of you recompute it?

gh workflow run pr-readiness.yml -f pr=15090 -f sha=dc57565e23af0f8f9f00de078167ff8695bd8984

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Sep 30, 2026

@bolichen97 bolichen97 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed on behalf of the maintainers (sweep 2026-09-30): readiness passed, required checks green on dc57565, no blocking review threads, security posture unchanged. Approving and merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fork Pull request from a fork (external contributor) readiness: passed Eligible automated validation passed for the current revision

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Sessions sidebar gets slow with a few hundred sessions

2 participants