| The roads I take... | Wie schnell wird SeaMonkey 2.1? >>

Weekly Status Report, W36/2010

Here's a summary of SeaMonkey/Mozilla-related work I've done in week 36/2010 (September 6 - 12, 2010):

We had a few messages recently about JavaScript speed and SeaMonkey, and it's quite fitting to those that the new "JaegerMonkey" method tracing just landed on the developement "trunk" and our nightlies this weekend. Out of personal interest and for calming people who fear we wouldn't work on speed, I did some runs of the popular SunSpider benchmark today. While the SeaMonkey 1.1.19 versions with which we announced the end of the line for the 1.x series comes in at 17501ms in that benchmark on my machine, a current SeaMonkey 2.0.x build comes in at 1738ms with the JS debugger enabled (default) and 1402ms with it disabled, which is a huge improvement - but just the baseline for current work. Now, today's pre-2.1 SeaMonkey build again just takes about a third of that baseline time and lands at 477ms - and the JaegerMonkey work isn't even finished yet. I think we are moving in the right direction. :)

Entry written by KaiRo and posted on September 13th, 2010 22:05 | Tags: L10n, Mozilla, SeaMonkey, Status | no comments | TrackBack

Comments

No comments found.

Add comment