Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

perf seems quantized around 1 second #24

Open
jchris opened this issue Nov 11, 2022 · 0 comments
Open

perf seems quantized around 1 second #24

jchris opened this issue Nov 11, 2022 · 0 comments
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization

Comments

@jchris
Copy link

jchris commented Nov 11, 2022

Screen Shot 2022-11-11 at 2 15 30 PM

This is chrome dev tools on a hard reset. The cache best case performance seems to be ~800ms. I wonder if there is something we can do to fix this. On naive content like the example app, fetches are serialized to it takes 1 second * 4 requests to go live. If there is some internal timeout we can adjust to cut this in half it would be huge
@jchris jchris added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Nov 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jchris