Gecko 1.9 intl rendering peformance
Boris Zbarsky
performance tests use significant intl content. By "intl" here, I
really mean non-ASCII.
If we're serious about improving intl support in Gecko 1.9, I believe we
need to create an intl performance page set or multiple intl performance
page sets (e.g. a BiDi page set, a CJK page set, a "western non-ascii"
page set, a CTL page set come to mind). Then we need to run at least
the pageload tests for all of these pagesets, and preferably also some
sort of DHTML tests using pages of the different types. We need to run
these tests on all three operating systems, since so much of the code
involved is platform-specific. For the same reason, ideally we would
run the tests on multiple variants of the operating systems (for
example, multiple Windows versions, Fedora Core 4, 5, 6 at least,
multiple OS X versions). I realize that's hard with our current
tinderbox setup, so I'll be happy if we just get the tests running at
all before the second alpha of 1.9.
The goal here is that once we have the tests set up we can do a Gecko
1.8 baseline so that we know what our performance goals for Gecko 1.9
are. If we can avoid regressing performance by too much from 1.8 while
adding the 1.9 features we're adding, that would be perfect. Of course
we're far from that goal right now. ;)
-Boris
Vladimir Vukicevic
> We have "intl" listed as a P1 task for Gecko 1.9, but none of our
> performance tests use significant intl content. By "intl" here, I
> really mean non-ASCII.
>
> If we're serious about improving intl support in Gecko 1.9, I believe we
> need to create an intl performance page set or multiple intl performance
> page sets (e.g. a BiDi page set, a CJK page set, a "western non-ascii"
> page set, a CTL page set come to mind).
I agree; the Trender pageset actually includes a chunk of these,
including CJK, some BiDi, etc. sets. These pages are sanitized; they're
sitting in my dir on fs. But we should be including them in Tp (or
rather, we should have another test that's like Tp, but run on just
these different categories of pages -- or Tp should have multiple
outputs -- or something).
- Vlad
Boris Zbarsky
> I agree; the Trender pageset actually includes a chunk of these,
> including CJK, some BiDi, etc. sets. These pages are sanitized; they're
> sitting in my dir on fs. But we should be including them in Tp (or
> rather, we should have another test that's like Tp, but run on just
> these different categories of pages -- or Tp should have multiple
> outputs -- or something).
Filed https://bugzilla.mozilla.org/show_bug.cgi?id=362758
Now how do I request blocking1.9 on it? ;)
-Boris