Closed Bug 105924 Opened 23 years ago Closed 18 years ago

store atom data as single-byte

Categories

(Core :: XPCOM, defect, P3)

Product:
Core
Component:
XPCOM
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 195262
Milestone:
Future

People

(Reporter: waterson, Unassigned)

Details

(Keywords: memory-footprint)

There are 118KB of atom data in the heap to bring up a single browser window. (This is before dbaron changed the implementation from a chained hashtable to a dhash, and I haven't yet measured with those changes.) Might be worthwhile storing atoms as UTF-8 strings, or take an even more hard-lined approach and just change the API to use single-byte characters.
Status: NEW → ASSIGNED
Keywords: footprint
Priority: -- → P3
Target Milestone: --- → mozilla0.9.7
There are places where we atomize things from user input (e.g., CSS classes and some XUL attribute values), so I don't think requiring single-byte characters would be easy. Nor would fixing this bug the other way, thanks to the |GetUnicode| method...
It looks like there is about 57KB of real atom data, not including the table overhead (which is now 32KB). So this is probably a win in the neighborhood of 20KB. Feh.
Target Milestone: mozilla0.9.7 → Future
Assignee: waterson → nobody
Status: ASSIGNED → NEW
QA Contact: scc → xpcom
*** This bug has been marked as a duplicate of 195262 ***
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.