Closed
Bug 17031
Opened 25 years ago
Closed 24 years ago
Necko protocol DLLs should be combined.
Categories
(Core :: Networking, defect, P3)
Tracking
()
VERIFIED
FIXED
M16
People
(Reporter: sfraser_bugs, Assigned: warrensomebody)
References
Details
(Keywords: perf)
Need to glob together all the small necko protocol DLLs, to make loading more efficient.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M12
Assignee | ||
Comment 1•25 years ago
|
||
I thought we had a bug on this already, but I can't find it now.
This bug is marked as for the Mac but I'm assuming this is something we want to do across platforms?
Reporter | ||
Comment 3•25 years ago
|
||
Yes, I think we should do this xp.
Assignee | ||
Updated•25 years ago
|
Target Milestone: M12 → M14
Assignee | ||
Comment 4•25 years ago
|
||
This isn't essential for dogfood. Moving to m14/beta.
Bulk move of all Necko (to be deleted component) bugs to new Networking component.
Updated•25 years ago
|
Keywords: perf
Summary: [Perf] Necko protocol DLLs should be combined. → Necko protocol DLLs should be combined.
Comment 6•25 years ago
|
||
Do you expect this to have a significant effect on load-time, enough to put this bug on the beta1 radar?
Comment 7•25 years ago
|
||
Question from PDT: Is this still an issue? Did we try pulling libs together for Mac during October and November, and conclude it was not the win we hoped for?? Thanks, Jim
Assignee | ||
Comment 8•25 years ago
|
||
We talked about this in the performance meeting today and think it will still be a win on Windows and Linux.
Comment 9•25 years ago
|
||
PDT wants to know why this is expected to be a win on Mac and Linux when it wasn't on Mac.
Assignee | ||
Comment 11•25 years ago
|
||
Info from Simon... Pros: 1. Reduce # items in components folder, reduce enumeration overhead 2. Eliminate per-library loading overhead 3. 'Cleanliness' Cons: 1. Harder to update just one protocol 2. May cause loading of more unused code at startup
Comment 12•25 years ago
|
||
Not essential for beta; do it at your leisure.
Whiteboard: [NEED INFO] → [PDT-][NEED INFO]
Assignee | ||
Comment 15•24 years ago
|
||
Want input from shrimp project as to which protocols they really need. That will help decide the best packaging. Assigning to selmer to get the input.
Assignee: warren → selmer
Status: ASSIGNED → NEW
Comment 16•24 years ago
|
||
Gayatri, this is yours now. Can you make a quick estimate based on the info you got from Varada?
Assignee: selmer → gayatrib
Assignee | ||
Comment 18•24 years ago
|
||
Taking this back.
Comment 19•24 years ago
|
||
Clearing [NEED INFO] to get on re-eval query for PDT.
Whiteboard: [PDT-][NEED INFO] → [PDT-]
Assignee | ||
Comment 20•24 years ago
|
||
Here's what I think we're going to do: nknet.dll (new) will contain what is currently in: necko.dll nkcache.dll nkhttp.dll nkfile.dll nkdata.dll nkjar.dll nkres.dll mimetype.dll nkabout.dll cnvts.dll stremcnv.dll Then nknet2.dll will contain the rest: nkdatetm.dll nkfinger.dll nkftp.dll nkkyword.dll (maybe this should go in the first one, or separate)
Assignee: gayatrib → warren
Status: ASSIGNED → NEW
Assignee | ||
Updated•24 years ago
|
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 21•24 years ago
|
||
It's in. They're called necko.dll and necko2.dll. Keyword is in the first one.
You need to log in
before you can comment on or make changes to this bug.
Description
•