Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upInvestigate per-document event queues #6281
Closed
Labels
Comments
|
Consider this for #5236. Advantages also include having to pass around far fewer PipelineId values and having the ScriptTask do much less routing. Additionally, any events queued after a document chooses to shut down can just be ignored, but they can also sit in the bfcache. |
|
Gecko's proposed model is the one we're already using. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we effectively have a per-origin event queue, and it's mixed in with the general script task events too. We should look into implementing a design like the one proposed for Gecko in https://bugzilla.mozilla.org/show_bug.cgi?id=715376, which yields benefits like tracking CPU usage per page (https://bugzilla.mozilla.org/show_bug.cgi?id=924582).