bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

investigate the cost of status/progress



17 years ago
14 years ago


(Reporter: Cathleen, Assigned: Bill Law)


Firefox Tracking Flags

(Not tracked)



(3 attachments)



17 years ago
please provide a patch to remove status/progress to the bug for further analysis.

Comment 1

17 years ago
Created attachment 57862 [details]
Patch to remove the entire status bar

This removes the entire status bar at the bottom of the Navigator window.  I
didn't try to remove the code loaded to support the "connection status"
indicator or the security icon.  Perhaps I should try removing just the
progress/status area of the status bar?  I've got tasks to remove the security
icon by itself.

Comment 2

17 years ago
Created attachment 57863 [details]
MOZ_TIMELINE output *with* the status bar

Comment 3

17 years ago
Created attachment 57864 [details]
MOZ_TIMELINE output for Navigator sans status bar

Compare this to the preceding attachment to see where the savings came from.

Avg time to start up with status bar: 5.995 seconds
Avg time to start up without status bar: 5.771 seconds

Savings: 0.224 seconds (3.7%)


17 years ago
Blocks: 7251

Comment 4

17 years ago
I removed just the status/progress panel from the status bar (and the 
corresponding JS code).  The savings was miniscule (0.36%).

We could, theoretically, defer the loading/creation of this panel till some 
point after startup (presuming the user could live without status updates while 
their initial page loads.  But the benefit is negligible so I don't think we 
should bother with that.

We can't remove the entire status bar.

Further work (other bugs) will examine other status bar panels (e.g., task bar, 
security icon, etc.).

Comment 5

17 years ago
Last Resolved: 17 years ago
Resolution: --- → FIXED

Comment 6

17 years ago
Bill, did your patch prevent all the messages targeted at the status bar from
even being sent, or did they just go in the bit bucket?  Would it matter to the
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.