Closed Bug 45671 Opened 25 years ago Closed 24 years ago

perf: WinEmbed kicks Seamonkey's ass.

Categories

(Core :: XUL, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED INVALID
mozilla0.9

People

(Reporter: gagan, Assigned: hyatt)

Details

(Keywords: perf)

On the weekend I spent some time running and comparing WinEmbed (a cool embed demo app that dougt wrote) and Seamonkey. One of the very interesting finds was that WinEmbed is consistently faster than Seamonkey by an order of 5 to 8 seconds per page load. We should consider investigating the difference in "features" that kick in for Seamonkey. These could be BIG wins for our performance. One related issue with this is that the WinEmbed bloat is significantly lower too. (per dougt's email- (from jud's investigation)) While this could be a separate bug I would leave this one here (as a meta reference) Notice the amount of data (in bytes) in memory (bloat) at the time "about:bloat" for each app... SeaMonkey: 898,984 Viewer: 856 WinEmbed: 1,440
winEmbed is like Viewer in that it does not use XUL as a UI and it does not use a bunch of the "browser-like" features (Bookmarks, Sidebar, Cookies, Wallet, ect). Viewer has always been faster than Seamonkey. I think it will always be this way. Running winEmbed and simply loading "http://people.netscape.com/dougt", you will not load any xul and most of the "features" in seamonkey are never used or loaded. In fact, if you ran nmake (unix coming soon) in mozilla/embedding/config you would only get the minimal dll's and files needed to browser webpages (or do simple editing). It would be interesting to identify all "optional" components and get numbers on how long each consume during URL loads.
Keywords: perf
QA Contact: sairuh → jrgm
Can I just say that I LOVE this bug title. I laughed for about 3 straight minutes when it first showed up in my mailbox. :)
hyatt can look at this while he's still laughing :-)
Assignee: don → hyatt
Component: XP Apps → XP Toolkit/Widgets
While WinEmbed may be a good place to look for ideas on improving Seamonkey, there is no specific Seamonkey defect reported in this bug. ->future to get off the nsbeta3 radar.
Target Milestone: --- → Future
->moz0.9
Target Milestone: Future → mozilla0.9
doh! resolving as invalid.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
invalids, wontfixes, dups, worksformes
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.