I gave another talk on code caching at Skills Matter, this time with a focus on JS developers: https://skillsmatter.com/skillscasts/12178-code-caching-for-js-developers …
-
-
It is very interesting that you choose not to code-cache scripts under 800B. I appreciate the fixed/base cost of opening a file on Windows would immediately lead to this choice. Would this same trade-off apply if the script and cache were already in RAM?
-
Under 1024B I believe. Disk/file overheads aren't the only concern, there's also the cost of serialization/deserialization and of IPC between the browser and renderer. We've got the isolate cache covering most of the "in RAM" cases anyway.
- Još 2 druga odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.