On 2/14/13 5:33 PM, Brian Anderson wrote:
* FFI stack switching - https://github.com/mozilla/servo/issues/278
* FFI virtual calls - https://github.com/mozilla/servo/issues/278
* DOM representation - https://github.com/mozilla/servo/issues/280
* string representation - https://github.com/mozilla/servo/issues/282
* optimizing layout requests - https://github.com/mozilla/servo/issues/283
3 of those are on the list for the new milestone. The string and layout
issues are not. Do you think it is appropriate to make either of those
part of the milestones for this year? Are there other critical
performance questions I'm forgetting?
In terms of DOM bindings, no, I don't think so.
I do think we should get our string story straight sooner rather than
later, or at least make sure we don't start depending too heavily on it
being a particular way.. I'd really hope we can do that this year.
A far as optimizing layout requests, I think that's more tuning that
will need to happen sometime, but isn't urgent as long as we can
demonstrate that we _can_ do it fast enough in a microbenchmark.
I hope this helps ease your mind somewhat
Oh, my mind was at ease already, more or less, on the DOM bits. We can
solve it; it's just a matter of timeframe...
I'm more worried about strings and cross-task communication.
For your reference, some of the performance issues you've raised
previously are already impacting Rust's design. Most significantly the
[FFI] is in the process of being redesigned to support servo's use case.
Also, the upcoming [scheduler] redesign should give us more
opportunities to experiment with optimizations relevant to servo.
That's really good to hear!
-Boris
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
