Quote:
Originally Posted by chaley
Calibre doesn't simply read the file into memory. Instead it builds a large number of data structures that increase memory usage by orders of magnitude. I have personal experience of a laptop with 1.5GB of RAM thrashing when I opened my 2400 book calibre library, taking minutes to start. A 200 book test library opened in seconds. Of course calibre wasn't the only thing running, but then calibre is *never* the only thing running. I ended up replacing that laptop. YMMV.
|
Just opened Calibre with my standard library, took about 2 seconds to open (i7-3820QM@2.7GHz laptop, 32GB RAM, Samsung 840 EVO 500GB Win7 x64). I use this laptop to do quite a bit of virtual machine work so needed the RAM and HD space.
I created a new empty library, closed Calibre and re-opened.
Old: 142,316KB memory, 50MB IO Read, 36KB IO write, 518KB IO Other
New: 104,372KB memory, 32MB IO Read, 40KB IO Write, 518KB IO Other
Not what I would call orders of magnitude increase in memory usage. 38MB of memory going from a 4.8MB to a 127KB database file.
Trying to measure the difference in startup times showed about .5 seconds more to open the full library compared to the empty library averaged over 5 trials.
Regards,
David