Blink now spawns an utility process for managing code cache when usingTakashi Nakayamanit: "a"
Done
Blink now spawns an utility process for managing code cache when usingTakashi Nakayamais this true? is it not just bouncing to another thread that it will use to talk to the browser process?
That's right. Thanks for pointing it out, I rewrote this sentence a bit (process -> thread, and "managing" -> "communicate").
base::TaskTraits GetTaskTraitsForCodeCacheProcess() {Takashi Nakayamanit: blank line after namespace open
Done
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
2 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: third_party/blink/renderer/platform/loader/fetch/persistent_code_cache_host.cc
Insertions: 1, Deletions: 0.
The diff is too large to show. Please review the diff.
```
[CodeCache] Assign high priority for PersistentCache fetch thread
Blink now spawns a utility thread to communicate to the browser process
when using PersistentCache for code cache, thus InlineScriptCache fetch
operations, which is conducted during the HTML parser by blocking the
main thread, is stalled while the utility process is not scheduled.
Assigning the highest priority for the utility thread will speed up
cache fetch.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |