Quote:
Originally Posted by theducks
 RAM as much as the OS supports (the motherboard/processor may support more, but the OS is the limiting factor)
Calibre will use as much CPU (core) as it can get if needed. Keep those fins and fans clean 
Each of those 3K books is getting its Metadata updated as it is sent which will eat time.
As you noted: Flash memory is not the fastest horse in the race  |
Already planning on 8GB RAM for the build. With 8GB kits going for $40, it doesn't make much sense to cheap out even more. Given 32-bit apps are limited to 2GB memory, I think 8GB RAM will be more than plenty. Will be using an SSD so the source drive shouldn't be an issue.
Yes, Calibre will use as much CPU as it can if needed. However, in this case, USB2 and flash memory speed will eventually be the bottleneck. Keep in mind, I won't be using it for conversion and from what I've seen (while I was still awake, anyway), sending books to the device only uses one core.
Quote:
Originally Posted by kiwidude
Personally I would suggest you rethink putting 3,000 items on your device. It will always be your device that is the weakest link in the chain slowing things down - the more books you put on there, the slower it will be every time you connect it to calibre as it has to read the database off it and iterate across its folders to find books that are not in your library etc.
|
In this case, I don't think it's the device that's the weakest link
yet. From what I can see, the transfer is divided into 3 stages: 1) initial prep? 2) file copying and 3) send metadata
Stages 1 & 3 are the ones taking up so much time. The actual file copying (3,171 files, 328MB) finished fairly quickly.
I'm not going to read all 3,000 ebooks. Reason I'm putting them on the reader is because most of them are probably crap and I plan to mark which ones to keep and which ones to delete on the reader itself.