@mathias does "code-caching" remove the need for "lazy-parsing" optimization in @v8js? In our project "lazy-parsing" is actually harmful for TTI (we can preparse ahead of time).
https://v8.dev/blog/code-caching …
https://v8.dev/blog/preparser
No, these are two separate optimizations. Code caching can only happen for warm loads. Lazy parsing speeds up cold loads.
Can you say more about your project? What makes you say lazy parsing is harmful? +@tverwaes @leszekswirski
-
-
It is a desktop app that has many view/windows (we use chromium). Loading consist of two parts: preloading a hidden view in background and showing it (this is TTI). At this moment the view morphs into a concrete view and we execute a bunch of js but it is lazy parsed, thus slower
-
So because we have time to do some work in background we don't mind slower parsing in exchange for faster execution later. Also worth mentioning that js content is known at build time for the app. Q: will producing cached data at build time eliminate lazy parsing?
- 5 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.