Has the logs table hit limits with TanStack Table + react-virtual?

[sahil598]

Disclosure first: I maintain EliteGrid (elitegrid.dev), so I have an interest here — tell me if this is unwelcome and I'll drop it.

HyperDX runs @tanstack/react-table with @tanstack/react-virtual for the log and trace views. I've been benchmarking that exact combination, and where it tends to hurt is sort and memory at high row counts rather than scroll.

Published runs, 1M rows / 8 columns / Chromium 149:

sort: 304 ms vs 4,666 ms
heap after mount: 104 MB vs 495 MB
Two caveats, both in our report: TanStack is headless, so those figures include a renderer we wrote and are not a verdict on TanStack Table itself; and TanStack beats us on mount at every size (1M: 1,383 ms vs our 1,769 ms). Full methodology, pinned versions and our losses: github.com/elitegrid/benchmarks

My actual question, and it's useful to me either way: for a log viewer, is browser memory at high row counts something your users hit, or does the time window usually keep result sets small enough that it never comes up? If it's the latter, that's genuinely useful for me to know.

I saw that PRs need a maintainer to vouch first, so I'm not proposing code — just asking whether the problem is real for you