Mozilla 0.9 Released!

Monday May 7th, 2001 today released milestone 0.9, which moves us a big step closer to a 1.0 release. The 0.9 release contains some of the largest changes in quite some time, with rewrites of the imglib, memory and disk cache, message view in mail, bookmark manager, Personal Security Manager 2 (PSM2), and the help viewer. Many of these rewrites have helped greatly enhance Mozilla's performance since 0.8.1, with the Mail front end rewrite and PSM2 being two of the largest improvements. For those of you who use Java, the JVM is now loaded on first use, rather than when you first start up, leading to much quicker startup.

Builds are currently available for Linux, Windows and Mac, on's download page. Expect other platforms to show up by the end of the week.

The next planned milestone is 0.9.1, for which the tree will close on May 23, and will be released a week or so following that date. Any milestone from this point forward has the possibility of becoming 1.0, and everyone is working hard to get the bug count down to make that happen.

#85 Some performance "measurements"

by dipa

Wednesday May 9th, 2001 1:10 PM

You are replying to this message

Below there are some startup performance and footprint measurements I made on two milestone and a nightly release. The system was a K6-III/400 with 192 MB ram, EIDE hard disk, Windows 98. Javascript for mail & news was always enabled.

Initial footprint measurements were extracted from Windows System Monitor, thus they aren't very accurate but at least they are reproducible.

v0.8.1 BROWSER (java enabled) : 13 sec v0.8.1 MAIL: (java enabled): 15 sec v0.8.1 BROWSER MEMORY FOOTPRINT: 17.5 MB

v0.9 release BROWSER: 9 sec (5 sec on reload) v0.9 release MAIL: 10 sec v0.9 release BROWSER MEMORY FOOTPRINT: 17.2 MB

Build 2001050904 BROWSER: < 8.5 sec (4.5 sec on reload) Build 2001050904 MAIL: 10 sec Build 2001050904 BROWSER MEMORY FOOTPRINT: 15.3 MB

As you see, startup time is 1 sec faster in current trunk builds (compared to 0.9 release) since they incorporate view source on demand. Footprint is also smaller but this is usual: trunk builds initial footprints are always a few MB smaller. Anyone knows why?