Closed Bug 45907 Opened 26 years ago Closed 26 years ago

Is DBM needed if the DiskCache is not used?

Categories

(Core :: Networking: Cache, defect, P3)

Product:
Core
Component:
Networking: Cache
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
CLOSED FIXED

People

(Reporter: rpotts, Assigned: jud)

References

Details

(Keywords: embed, memory-footprint, Whiteboard: [nsbeta3+])

In embedded clients which do not use the disk cache, we should not require the DBM DLL... This will require breaking out the disk cache from the necko.dll... -- rick
Keywords: embed, footprint, nsbeta3
Split out the disk cache and dbm, but leave the memory cache, right?
exactly.
this should be a big win.
Whiteboard: nsbeta3+
does the mem cache use a memory version of dbm?
Whiteboard: nsbeta3+ → [nsbeta3+]
This depends on bug 47405
Depends on: 47405
dbm is not needed in this case. however, on windows, due to linking constraints we still have to link it into the core necko dll. To remove dbm you need to remove filecache from the build (and refs to it in /netwerk/cache/build and /netwerk/build). The extra step on windows is to remove the dbm link in netwerk/build/makefile.win
Assignee: dougt → valeski
Wait... I was advocating using the memory cache to fix the "throbber hits the disk" problem. If we do that, we'll need dbm after all. How big is it?
? memory cache doesn't use dbm. are you saying you want to hook it up to do so? dbm on linux debug is 280k bytes.
Target Milestone: --- → M18
Never mind. I was confusing the 2 caches.
this has been resolved. see above comments.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
development issues - closing based on engineers comments
Status: RESOLVED → CLOSED
You need to log in before you can comment on or make changes to this bug.