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

Implement blocking strategy for writing to busy DOM nodes #232

Closed
brson opened this issue Dec 8, 2012 · 2 comments
Closed

Implement blocking strategy for writing to busy DOM nodes #232

brson opened this issue Dec 8, 2012 · 2 comments

Comments

@brson
Copy link
Contributor

@brson brson commented Dec 8, 2012

Our current implementation uses copy-on-write, but there is some skepticicsm about how performant this will be. Simply blocking and waiting for layout to finish could be faster than copying nodes. A blocking strategy would also eliminate a pointer indirection on each node. There is work that content can do while waiting (GC).

It should be possible to create a single interface that supports both strategies. For the sake of measurement this seems like a worthwhile thing to do.

@brson
Copy link
Contributor Author

@brson brson commented Feb 14, 2013

Recent discussions between @pcwalton and @bzbarsky may indicate that this isn't desirable after all.

ChrisParis pushed a commit to ChrisParis/servo that referenced this issue Sep 7, 2014
Update format-field-retry.htm
@jdm
Copy link
Member

@jdm jdm commented Oct 21, 2014

We currently block, except when we don't. But should.

@jdm jdm closed this Oct 21, 2014
glennw pushed a commit to glennw/servo that referenced this issue Jan 16, 2017
Try to make the GPU profiling code compile on Gonk.

r? @glennw
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.