Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Experimental throttling mode to avoid putting much load on the CPU #3913

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

philipp-classen
Copy link
Member

Experimental throttling mode to avoid putting much load on the CPU if there are bursts of DOM modification events, even though there are no changes.

It keeps a set of elements for which most mutations will be skipped.

Context:

refs ghostery/ghostery-extension#757
refs ghostery/ghostery-extension#1392

The best way to reproduce the high CPU load is to use the standalone extension and uBlock Origin together, as described here:
ghostery/ghostery-extension#757 (comment)

Test sites are reddit.com and heise.com. In both cases, the CPU load on Firefox reduces. But note that having dev tools open kills performance. With the console.warn, it can be observed later if a website triggered throttling mode temporarily.

if there are bursts of DOM modification events, even though there are
no changes.

refs ghostery/ghostery-extension#757
refs ghostery/ghostery-extension#1392
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant