Re: gconf backend

On Sat, Sep 27, 2003 at 01:51:09AM -0400, Havoc Pennington wrote:
> On Sat, 2003-09-27 at 00:49, Havoc Pennington wrote:
> > 
> > The new gconf backend I wrote a year ago seems to use about 50% of the
> > memory of the current one
> Or better, "gconftool-2 -R /" on my system (my .gconf has years worth of
> cruft in it) uses 53M with the old backend and 10.5M with the new. (the
> -R / means the whole gconf tree is cached in the daemon for a few
> minutes, so is the maximum possible mem usage)

  What is the difference technically speaking  ?

How do you parse the XML files, I'm making new APIs for libxml2 [2] which
I plan to introduce in the upcoming libxml2-2.6.0 which can significantly
speed up parsing of a large number of files based on the same grammar,
by allowing reuse of parser context (and all the internal state associated
like the dictionary used to intern strings). If gconf uses libxml2 then
considering the nature of the files and their number this could lead to
serious performance improvement in accessing the data (using mmap'ed
files with the memory interface also proves to increase speed, but
remove the default support for compressed XML found for files access [1]).


[1] the main speedup in using the mmaped files is that it bypasses the
    gzip IO layers which slows the access even for non-compressed files.

Daniel Veillard      | Red Hat Network
veillard redhat com  | libxml GNOME XML XSLT toolkit | Rpmfind RPM search engine

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]