Do we know what *part* of page load got slower? is it anything in
layout (style resolution, reflow, etc.?) marc's perf tests run on code
before and after the slowdown could help identify (or at least
eliminate) what areas got slower.
Chris Waterson wrote:
> We have still made zero progress on this:. A week has gone by, and page
> load is still down by 13%. Here are the people that are on the hook
> during the time that the slowdown occurred. If I made a quick look
> through the deltas
>
>
> http://bonsai.mozilla.org/showcheckins.cgi?&treeid=SeaMonkey&batchid=453
>
> If had to guess, I'd say that darin and ftang should be reviewing their
> changes...
>
> chris
>
> Chris Hofmann wrote:
>
>> ----------------------------------------------------------------------
>> The following people are on "the hook", since they have made checkins
>> to the tree since it last opened:
>>
>> Who What
>> Peter.VanderBeken%pandora.be2 changes
>> av%netscape.com 1 change
>> axel%pike.org 7 changes
>> beard%netscape.com 1 change (1 while tree closed!)
>> ben%netscape.com 1 change
>> bienvenu%netscape.com 2 changes
>> blakeross%telocity.com 10 changes
>> brade%netscape.com 1 change
>> ccarlen%netscape.com 14 changes
>> cls%seawood.org 1 change
>> darin%netscape.com 34 changes (2 while tree closed!)
>> dbaron%fas.harvard.edu 5 changes (4 while tree closed!)
>> dmose%mozilla.org 1 change
>> dr%netscape.com 1 change
>> jj%netscape.com 1 change (1 while tree closed!)
>> kin%netscape.com 19 changes
>> mcafee%netscape.com 8 changes (8 while tree closed!)
>> mkaply%us.ibm.com 4 changes (2 while tree closed!)
>> mscott%netscape.com 2 changes
>> neeti%netscape.com 1 change
>> nhotta%netscape.com 1 change (1 while tree closed!)
>> racham%netscape.com 15 changes
>> radha%netscape.com 1 change
>> sspitzer%netscape.com 1 change
>> timeless%mac.com 2 changes
>> yokoyama%netscape.com 1 change
>> 137 checkins.
>
