Quote:
Originally Posted by kovidgoyal
That's insane. What do you have in your databases? The entire text of books? Memory usage is approximately:
constant1 + constant2 * size of metadata.db
because the entire metadata.db is laoded into RAM (but unpacked and stored in an object layout for speed). Custom columns behave no differently from builtin ones. For every column that you have the required memory goes up by size needed for an entry in the column * number of books in the library (technically it is not quite that large, because empty items use less memory for most column types). Both constant1 and constant2 are only approximately constants. I've made them constant only to simplify the discussion.
On my machine with a library with 50,000 books, calibre uses 600MB. With a library of 1000 books it uses 100MB.
The content server does not use any significant amounts of memory, but that is easy to test, simply turn it off and compare memory with it on and with it off.
|
Ok That I understand. My metadata.db is at 418695. There are around 240,000 books. I have 12, soon to be 13 custom columns. I replace tags with my own to help me determine what I want to read next...
The comments are filled in as I search for ID links and I usually use Goodreads if it is available.
Not sure if it matters but the custom columns are 4 y/n/blank, 1 date, 1 built from other columns and 7 text columns.
It makes no real difference if the content server is on or off for loading time or memory usage.
After restarting Calibre several times and checking what preferences and columns were set, for some reason the time to enter Calibre is under a minute (25 seconds). Earlier today it took much longer to load. My system at this time has two text editors with a total of 6 ascii text windows open. Chrome with 9 tabs (that's kind of light, usually have about 22 or so tabs open) and Firefox with 6 tabs. ummm I also have mirc and ultrafilesearchlite running and of course task manager. Oh yes, I also have three explorer windows open and one calibre ebook viewer open.
The version of Calibre that I have installed is 2.66 (I only download when there is a significant change or I have a problem) but I didn't see anything about memory management in the update notes when I looked at them.
Calibre had been open for about three days without being closed when I noticed it was using 2400meg. That seemed to be a bit much. I had been downloading metadata and doing conversions and adding tags and saving selected files to disk. Oh yes, I had also been running duplicate file search and checking each of the files to see which to keep.
Some of my custom columns are nearly empty but... I may create a duplicate of this library and see how much difference in memory usage there is as I start delete the custom columns.
By the way, I was not complaining about the memory usage. Just started looking at it as I can't afford a laptop with near as much ram as my desktop system and wanted to see just what my normal usage was to see how tight things would be.