Closed Bug 407977 Opened 18 years ago Closed 10 years ago

possible performance improvement: hard-code the richlistitems in autocomplete.xul

Categories

(Firefox :: Address Bar, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: moco, Unassigned)

Details

(Keywords: perf)

possible performance improvement: hard code the richlistitems in autocomplete.xul another suggestion from vlad. Right now, in _appendCurrentResult() in autocomplete.xml, when the user first starts typing in the url bar the very first time (for each window), we will create the richlistitems: 979 if (this._currentIndex < existingItemsCount) { 980 // re-use the existing item 981 item = this.richlistbox.childNodes[this._currentIndex]; 982 } 983 else { 984 // need to create a new item 985 item = document.createElementNS("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul", "richlistitem"); 986 } by default, browser.urlbar.maxRichResults is currently 25 so if in autocomplete.xml our content for the richlistbox had 25 richlistitems, we wouldn't pay a performance price when the user starts typing instead we'd pay it on Ts / Txul, though, I believe, but keep in mind that the panel is hidden. note, maxRows is currently 10 (http://lxr.mozilla.org/seamonkey/source/browser/base/content/browser.xul#264)
Summary: possible performance improvement: hard code the richlistitems in autocomplete.xul → possible performance improvement: hard-code the richlistitems in autocomplete.xul
I don't think it's worth to micromanage perf at this level, it only happens once per window, most users have just 1 window and it's important that it appears as fast as possible. Moving the cost to Ts or TXul wouldm't be wise. Morever we're at 12 results and will very likely reduce to 8 soon. The cost is very contained.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.