woutdp/live_svelte

Improve performance SSR rendering

Open

#36 建立於 2023年4月27日

在 GitHub 查看
 (5 留言) (4 反應) (0 負責人)Elixir (1,646 star) (73 fork)batch import
enhancementhelp wanted

描述

Currently SSR takes about 8ms each render in production, and about 20-40ms in dev, and this is being executed synchronously. So let's say you have 10 components inside a LiveView, it'll end up taking 80ms!

When turning off SSR it's super fast, you can easily render a 100 components and not feel any delay.

The culprit is the call to NodeJS.

Doing the following things will probably do the trick.

  • Reduce the amount of time to call NodeJS
  • Run asynchronously somehow, I'm not sure how to do this inside a HEEx template.

Maybe Bun is the answer here, or a better way of calling Node.

貢獻者指南

技術棧
elixirsveltenodejs
領域
performancebackend
議題類型
performance
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Elixir basicsPhoenix LiveViewSvelte
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
The issue identifies that SSR performance is bottlenecked by synchronous NodeJS calls. To improve, investigate the SSR implementation in the repository, likely in files like `lib/live svelte/ssr.ex` or similar. Profile the NodeJS calls to understand the overhead and explore batching multiple component renders into a single Node call. Consider making the calls asynchronous using Elixir tasks or pooling NodeJS processes. Also evaluate whether Bun can replace NodeJS for faster startup times. Review the comments for maintainer feedback on possible approaches.