fastload pref files ( 4.1% startup)

VERIFIED WONTFIX

Status

()

defect
VERIFIED WONTFIX
18 years ago
5 years ago

People

(Reporter: cathleennscp, Assigned: bnesse)

Tracking

({perf})

Trunk
mozilla1.2alpha
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

18 years ago
 
Reporter

Updated

18 years ago
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
Reporter

Updated

18 years ago
Depends on: 98533
Assignee

Updated

18 years ago
Target Milestone: --- → mozilla1.0

Comment 3

18 years ago
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
Assignee

Updated

18 years ago
Depends on: 132140

Comment 4

16 years ago
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.

Comment 5

15 years ago
Should this bug be closed on out?
Yes, it should be closed.

/be
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.