Closed Bug 17032 Opened 26 years ago Closed 14 years ago

Browser component DLLs should be combined

Categories

(SeaMonkey :: UI Design, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME
Future

People

(Reporter: sfraser_bugs, Assigned: jag+mozilla)

References

Details

(Keywords: perf, Whiteboard: [nav+perf])

In an effor to reduce the number of small DLLs, we need to combine the browser component DLLs (which can usefully be combined) into a single larger DLL.
Blocks: 17033
Summary: [Perf] Brower component DLLs should be combined → [DOGFOOD][Perf] Brower component DLLs should be combined
Whiteboard: [PDT-]
PDT- should be porkjockey, not dogfood.
Status: NEW → ASSIGNED
Priority: P3 → P1
Target Milestone: M12
Do this for M12.
Target Milestone: M12 → M13
Move to M13 since this is not dogfood.
Keep Simon in the loop as this may conflict with his 5085 where he was talking about *splitting* libraries (reconfiguring, actually) so less is loaded at startup.
Summary: [DOGFOOD][Perf] Brower component DLLs should be combined → [Perf] Brower component DLLs should be combined
Whiteboard: [PDT-]
Target Milestone: M13 → M15
Not required for beta 1.
Keywords: perf
Summary: [Perf] Brower component DLLs should be combined → Broswer component DLLs should be combined
Moving "perf" to keyword field. This is the are we use now :-)
Move to M16 for now ...
Target Milestone: M15 → M16
Target Milestone: M16 → Future
Judson, do we need to do this too? I still see the following small browser component DLLS that could be combined: AppShellDebug.shlb ? FindComponentDebug.shlb mozBrowserDebug.shlb shistoryDebug.shlb ucthDebug.shlb webBrowserDebug.shlb xferDebug.shlb
I consolodated those, on all platforms, which I was able to do (without diving into law's specialized/complex APP_MODULE_MACRO thing). The list you show contains those that weren't easily consolodated or should be left independent as they are candidates for replacement by embedding parties.
adding some nomination keywords.
Keywords: mozilla0.9, nsbeta1
nav triage team: Would be very nice, but not critical for beta1. Marking nsbeta1-, more important things to work on would be making xpcom startup faster
Keywords: nsbeta1nsbeta1-
QA Contact: don → sairuh
Summary: Broswer component DLLs should be combined → Browser component DLLs should be combined
Blocks: 71874
P1/Future? Strange combination. Any plans for this soon?
Keywords: mozilla0.9mozilla0.9.1
nav triage team: Umm, won't the "static" build get us this?
Yes, but with the static build, we lose all the advantages of the component system. We currently have lots of DLLs (about 90), and I'd bet this number could be cut in half without too much pain.
Whiteboard: [nav+perf]
Changing platform
Hardware: All → Macintosh
OS: Mac System 8.5 → All
Hardware: Macintosh → All
Product: Core → Mozilla Application Suite
As of Firefox 3.0b2, only two DLLs are in the components directory: browserdirprovider.dll brwsrcmp.dll bsmedberg, stuart: Are these DLLs which could go into libxul or are they best off staying separate?
Assignee: law → jag
Status: ASSIGNED → NEW
QA Contact: bugzilla
Oh, and I'm assuming that Seamonkey will be in a similar position once libxul is enabled, yes?
They should not be in libxul: libxul is the platform by design, and Firefox is built on top of it. You could theoretically combine the two DLLs into one, but it won't affect performance noticably.
WFM: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b12pre) Gecko/20110212 Firefox/4.0b12pre SeaMonkey/2.1b3pre Only suite.dll left
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.