How GitHub Issues improved navigation performance with client-side caching and prefetching
How the GitHub Issues team used client-side caching, smart prefetching, and service workers to make navigation feel instant.
Read the full articleYou might also wanna read
GitHub Investigating Increased Latency and Performance Issues in API Services
GitHub's Status Page - Incident with search on GitHub we are seeing increased failure rates.
githubstatus.com·11mo ago
GitHub's UI Performance Decline: A User's Frustration
Matyáš Racek's blog
yoyo-code.com·11mo ago
GitHub Performance Issues on Safari: Pages Take 10+ Seconds to Load
Select Topic Area Bug Body Over the past few months, Github has been getting slower and slower on Safari. It has now reached a point where i
github.com·10mo ago
GitHub mitigates degradation affecting Actions and Pages services
GitHub's Status Page - Incident with Actions and Pages.
githubstatus.com·1mo ago
GitHub's reliability crisis: AI-driven load surge or self-inflicted wounds?
GitHub’s leadership blames the 3.5x increase in service load as the cause of degradation – or it might be self-inflicted.
blog.pragmaticengineer.com·1mo ago
Improving GitHub Actions Cache Performance Through Reverse Engineering
We reverse engineered GitHub Actions cache internals to transparently route cache requests through our faster, colocated cache. This deliver
blacksmith.sh·11mo ago
Comments
Sign in to join the conversation.
No comments yet. Be the first.