Re: [Tracker] more issues with indexer-split

Jamie McCracken wrote:
On Tue, 2008-09-02 at 12:23 +0100, Martyn Russell wrote:
Jamie McCracken wrote:
Could we also reduce memory usage by not statically linking to the
private libs libtracker-common and libtracker-db?
Those libraries should not be available for public use. Before doing so,
each API would have to be:

a) Documented
b) Checked it needs to be public
c) Versioned
d) ...

This is a lot of work and I don't think it is worth it.
I haven't looked at the footprints myself though.

currently my FTS module and the file-indexer-module are ~ 1MB in size
due mostly to linking with them and im sure the size of trackerd and
tracker-indexer could be made smaller too with only one instance of
those libs in memory
How does the memory footprint compare to the old tracker?

having looked at the contents of libtracker-common, most of the memory
used is for the stemmers - we load them all into memory even though we
only use one of them. i think making each language stemmer a dynamically
loaded module should help reduce things

I can look into doing this.


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