Closed Bug 110908 Opened 23 years ago Closed 20 years ago

fastload pref files ( 4.1% startup)

Categories

(Core :: Preferences: Backend, defect)

Product:
Core
Component:
Preferences: Backend
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED WONTFIX
Milestone:
mozilla1.2alpha

People

(Reporter: cathleennscp, Assigned: bnesse)

References

Details

(Keywords: perf)

Blocks: 7251
Does this apply just to default prefs, or to use prefs as well?
Component: Browser-General → Preferences: Backend
Keywords: perf
QA Contact: doronr → jrgm
I talked to dp about this the other week, and we reckoned that this should not be pursued until we've fixed bug 98533 ("Remove JS from prefs backend"). Then, there may be no gain. /be
Depends on: 98533
Target Milestone: --- → mozilla1.0
Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+, topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword. Please send any questions or feedback about this to adt@netscape.com. You can search for "Moving bugs not scheduled for a project" to quickly delete this bugmail.
Target Milestone: mozilla1.0 → mozilla1.2
Depends on: 132140
Please, don't do any 'fastload' business on the preferences file. A good optimized and tuned parser can be as fast as a binary thing, which must also do parsing and verifing anyway. The most time consuming factor is find and load the file for it anyway.
Should this bug be closed on out?
Yes, it should be closed. /be
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.