To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=50842
                  Issue #:|50842
                  Summary:|memory / bloatage ...
                Component:|whiteboard
                  Version:|OOo 2.0
                 Platform:|All
                      URL:|
               OS/Version:|All
                   Status:|NEW
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P3
             Subcomponent:|lingucomponent
              Assigned to:|mmeeks
              Reported by:|mmeeks





------- Additional comments from [EMAIL PROTECTED] Thu Jun 16 08:21:07 -0700 
2005 -------
Just doing some memory profiling on OO.o and noticed hashmgr chewing
2Mb of space. I was wondering whom to talk to about fixing that.

        The size breakdown (for my dict: 46k strings), is: ~1Mb for the base
hash, and ~1Mb for all the strings [ plus malloc overhead of course ].

        AFAICS there is no need to dup the strings - they have great
terminators, we can (on unix) mmap the file [ otherwise just dup it
in-place ]. Then we can use a sparse array of 'char *' for the hash; and
bingo ;-) only ~400k instead of 2Mb+overhead, with some trivial performance 
loss.

        Of course, if you're interested in accepting that patch; I'll do a more
invasive re-factor to cleanup the hashmgr interface so that the hentry
is not exposed as part of the API - either way; for an hour or two of work
on my part - that'd make a nice saving; are you interested ? & to whom
should I talk ? about getting it up-stream ?

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to