You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Significant performance impact when using remote functions聽#14747
We have been exploring using remote function for the new LayerChart docs but have been encountering some performance issues (and I could 馃挴 be holding them wrong or have a bug in LayerChart).
For example, AreaChart has 5 examples which fetch large data from /static/*via prerender().
Loading the AreaChart page from navigation can take over 1 min
CleanShot.2025-10-17.at.09.52.47.mp4
but oddly if you refresh the page it only takes about 8 seconds
CleanShot.2025-10-17.at.09.58.33.mp4
I created an AreaChartSimple page which comments out these 5 examples, and navigation takes about 5 seconds
CleanShot.2025-10-17.at.10.12.55.mp4
The current docs takes about 4 seconds to a load all the examples (using +page.tsload())
CleanShot.2025-10-17.at.10.02.06.mp4
Note: There are some known performance regressions since ~5.36.0, but this is much more significant.
Reproduction
Check out LayerChart PR 659 and run pnpm dev (or run pnpm package in packages/layerchart and pnpm dev in docs)
Navigating to AreaChart or any other route using remote functions (search $derived(await) will present the slow performance on navigation. See AreaChartSimple or other routes which do not use remote functions for comparison.
You can also run the current docs by running pnpm dev:svelte in packages/layerchart
Is this still an issue given all the recent perf work in Svelte? i.e. if you update to the latest version does it still drop in perf compared to not using remote functions?
Hey @dummdidumm, thanks for following up. The significant performance issues initially reported have definitely been fixed, thanks!
We still see some minor performance regressions in Svelte compared to pre-async (<=5.35.0) especially when compared to LayerChart's pre-async/remote functions docs, but nothing to the point of blocking an upgrade at this point. We have these being tracked in sveltejs/svelte#17176, although they are at a level now that you need to compare before/after, as generally things feel pretty good. I've even considered closing #17176, but do think there is some opportunity left worth tracking.
Thanks to the team for all the hard work! We really appreciate it 馃
Activity
dummdidumm commentedon Feb 7, 2026
Is this still an issue given all the recent perf work in Svelte? i.e. if you update to the latest version does it still drop in perf compared to not using remote functions?
techniq commentedon Feb 7, 2026
Hey @dummdidumm, thanks for following up. The significant performance issues initially reported have definitely been fixed, thanks!
We still see some minor performance regressions in Svelte compared to pre-async (
<=5.35.0) especially when compared to LayerChart's pre-async/remote functions docs, but nothing to the point of blocking an upgrade at this point. We have these being tracked in sveltejs/svelte#17176, although they are at a level now that you need to compare before/after, as generally things feel pretty good. I've even considered closing #17176, but do think there is some opportunity left worth tracking.Thanks to the team for all the hard work! We really appreciate it 馃