Skip to content

perf(frontend): throttle TPS chart updates to 10 Hz - #112

Merged
iamvukasin merged 1 commit into
mainfrom
kjs/tps-perf
Aug 6, 2026
Merged

perf(frontend): throttle TPS chart updates to 10 Hz#112
iamvukasin merged 1 commit into
mainfrom
kjs/tps-perf

Conversation

@kyscott18

@kyscott18 kyscott18 commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

The frontend’s performance in production progressively degrades during prolonged operation. I identified the TPS chart as the main source of issues using CPU, memory, and React render profiling. It's fixed by limiting TPS updates to 10 Hz.

Greptile Summary

Limits the TPS chart’s sliding-clock state publications to 10 Hz to reduce sustained Recharts rendering overhead while retaining requestAnimationFrame’s hidden-tab pausing behavior.

  • Adds a 100 ms sliding-clock interval.
  • Gates setNow calls using the animation-frame timestamp.
  • Updates documentation to describe the throttled clock.

Confidence Score: 5/5

The PR appears safe to merge, with no concrete blocking or independently actionable non-blocking issue identified.

The throttled animation-frame loop preserves monotonic chart updates, continues scheduling frames, cancels the active frame during cleanup, and leaves incoming TPS data updates independent.

Important Files Changed

Filename Overview
frontend/components/network-activity-tracker/tps-chart.tsx Throttles sliding-clock publications to 10 Hz without changing TPS ingestion, interpolation semantics, cleanup, or chart-domain behavior.

Reviews (1): Last reviewed commit: "tps perf" | Re-trigger Greptile

@vercel

vercel Bot commented Aug 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
monode Ready Ready Preview Aug 5, 2026 10:03pm

Request Review

@iamvukasin
iamvukasin merged commit fbcabf2 into main Aug 6, 2026
10 checks passed
@iamvukasin
iamvukasin deleted the kjs/tps-perf branch August 6, 2026 08:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants