Not sure that's part of the benchmarks, but creating a file:// or chrome:// URI currently causes main thread I/O (bug 890712, iirc). That's certainly a big cause of slowdown.
Cheers, David On 06/05/15 04:07, Boris Zbarsky wrote: > On 5/5/15 9:58 PM, Doug Turner wrote: >> Performance. > > Note that performance has been a recurring problem in our current URI > code. It's a bit (10%) slower than Chrome's, but about 2x slower than > Safari's, and shows up a good bit in profiles. Some of this may be due > to XPCOM strings, of course, and the fact that there's a lot of > back-and-forth between UTF-16 and UTF-8 involved, but some is just the > way the URI parsers work. So yeah, if we can get better performance > that would be nice. ;) > > -Boris > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform -- David Rajchenbach-Teller, PhD Performance Team, Mozilla
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
