Closed Bug 14294 Opened 26 years ago Closed 26 years ago

_GetPref() & _GetBoolPref() called many times

Categories

(Core :: Layout, defect, P1)

defect

Tracking

()

VERIFIED INVALID

People

(Reporter: mcafee, Assigned: mcafee)

Details

(Keywords: perf)

linux, apprunner, debug. The functions _GetPref() & _GetBoolPref() in nsBaseWidget.cpp are called many, many times as running the app. Can we cache this somehow? This seems like a waste to me. Yeah it's debug, but we should look for speedups here too.
The prefs service is cached. To cache the pref value, you would have to code pref callbaks or something. This is debug only code, and there are much bigger fish to fry. So i dont plan on fixing it.
Assignee: ramiro → mcafee
stealing this little fish.
Target Milestone: M12
Whiteboard: [Perf]
Do we need to fix the for M12?
Target Milestone: M12 → M14
m14
OS: Linux → All
Priority: P3 → P1
Hardware: PC → All
Hmmmm, methinks this may be what's making the prefs dialog so slow (something that Rob Malda complained about in Slashdot M12 announcement). It would be really nice to fix this for beta 1. How hard is it?
Summary: Performance: _GetPref() & _GetBoolPref() called many times → [PERF] _GetPref() & _GetBoolPref() called many times
Whiteboard: [Perf]
moving perf to summary
spam: added self to cc list as this might affect my realm.
Keywords: perf
Summary: [PERF] _GetPref() & _GetBoolPref() called many times → _GetPref() & _GetBoolPref() called many times
Moving "perf" to keyword field. This is the are we use now :-)
m15
Target Milestone: M14 → M15
It's a debug build, and it's probably the paint-flashing stuff. We don't care about performance of debug builds.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
Marking verfied invalid per last comments.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.