Skip to content

perf: trim unused GitHub profile fields before serialization - #10

Draft
ofershap wants to merge 1 commit into
mainfrom
perf/compact-profile-data
Draft

ofershap wants to merge 1 commit into
mainfrom
perf/compact-profile-data

Conversation

@ofershap

Copy link
Copy Markdown
Owner

Project GitHub REST responses to the existing typed display fields before storing categories in RSC/ISR. TypeScript types alone do not remove raw REST properties.

  • Preserves all 13 GitHubRepo and 13 GitHubUser fields, nulls, zeroes, order and input objects.
  • No layout, cache policy, middleware, dependency or billing changes.
  • Adds contract and consumer-field regression tests.

Validation: 5 tests, TypeScript, Next and OpenNext builds pass. A public-data Ofer fixture reduces category JSON from 550,797 to 51,314 bytes and full rendered HTML from 874,137 to 341,819 bytes. Desktop/mobile/search fixture screenshots match. On a separate supported-runtime experiment, local workerd screenshots also match and both remote public-data variants render.

This is a payload reduction, not a verified cold CPU fix. Native provider metrics returned a combined unknown-script group and cannot attribute a CPU improvement. The existing runtime's manifest-load failure also prevents treating its fixture as a native comparison. Keep draft until release review. Separate from the supported-runtime dependency change and cache PR #8.

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.

1 participant