Quote:
Originally Posted by DNSB
~10,000 books at the moment. I tried opening calibre in a VM with a smaller library and the open time was not all that different. Oddly, though both cases took approximately 0.33 seconds from "[0.06] Initializing db...
[0.39] db initialized".
|
I'm sorry my man, that's like, not even a 1/3rd of the books that are on my book reader, let alone my library. I don't want to get into how many books I had loaded into calibre but that's not even a percentage point.
Quote:
Originally Posted by DNSB
I get enough command line at work. ESXi, Windows Server Core and 6 or 7 Linux boxes and one lonely Mac OS X system. Note that other than the ESXi servers, the other systems are virtualized. If I move on to the switches and firewalls, I can spend the entire day using Putty for CLI sessions.
|
That's cool but no offense, I'm not impressed. You use Windows.
Quote:
Originally Posted by DNSB
While I can make a fire by using flint and steel or a fire bow. I prefer to use a lighter when one is available.
|
Quote:
Originally Posted by DNSB
And I still find it humourous that you claim to be able to handle those tasks even using scripts in under 5 seconds.
|
And I find it sad that you seem to have missed that it took 15 minutes for calibre to load for me given the amount of books I had loaded into it at the time. My library is not ~10000 books.
Quote:
Originally Posted by DNSB
As I said, if nothing else, calibre handles the series information for a Kobo ereader in a much more pleasant fashion than editing the SQLite database. How does your script handle downloading, resizing and inserting covers into the ebook? The same for metadata such as series.
|
I don't use a Kobo so I have no need to edit any SQLite dbs. All of my ebooks have covers. I have no need to resize or insert. The series information is in the filename so I use my ereaders search functionality
to find what I need. I don't have to do anything but load books and read them.
Quote:
Originally Posted by DNSB
Oddly, I find your 15 minutes load time to be about as humourous as your reaction to my using Windows. Comparing that to my 4.36 seconds? Makes me wonder just how out of date your mass storage is.
|
Yea, it's my mass storage. That must be what it is. ZFS sucks. It has nothing to do with the fact that 10,000 books isn't even half of a half of a percentage point compared to me.
Well, tell you what, I'm currently loading the A*s into calibre. When that's done, (I'm on record 16033, at the moment), I'll time how long it takes calibre to load and I'll report back as I go though the B* and C* and so on.
Quote:
Originally Posted by DNSB
As for using Google cloud drive with calibre? The first question is what are you calling Google cloud drive? Google Drive for home users? Google Cloud Storage for enterprises? A utility that maps Google Drive as a storage device?
|
Google Cloud Storage using rclone.
Quote:
Originally Posted by DNSB
The last time I tested on a computer where Google Drive was used to sync, as long as a single computer is used and synchronization was paused before calibre was started and restarted after calibre exited, it seems to work (a batch file took care of that when I was doing some testing). My library backups are synced to the cloud but I found no real advantage to using cloud storage for my live calibre instance.
|
I am doing a unionfs approach, where I have a local encrypted calibre dir mounted to a dir that also has Gcloud mounted, where all local operations will be written to local disk and the encrypted view periodically uploaded to gcloud. I am not uploading the calibre dbs.
I'm actually still in the process of sorted my main library, so once I do that, I'll upload to gcloud just to offset my local storage. My main library is pretty big
I'm just testing calibre to make sure it works as expected, which so far, it has. I may keep it, I may not.