Quote:
Originally Posted by DoctorOhh
I use Dropbox and I just installed calibre cloud and searching is very quick and as soon as I go to an author the covers are shown very quickly. These are not cached as it was not on this device until just now and all of the dates for everything is current. Additionally it is only showing 961 items so I know it is grabbing the covers out of the cloud. When I fling it to a certain area it fills the 15 covers showing from Dropbox in about 3 seconds.
I only give you this info because the cover grabs from the cloud seem to be quicker then your estimates.
|
I found a few cases where I was doing the same work twice and fixed them. Here are some new numbers. These come from my Galaxy Nexus, a rather slow phone, so I think they are on the high side. Someday I will try it on my N5.
Code:
Downloading 5 covers:
Cover 1: 1160 milliseconds
Cover 2: 491 milliseconds
Cover 3: 587 milliseconds
Cover 4: 476 milliseconds
Cover 5: 571 milliseconds
In all cases CC requires around 200 milliseconds to resize the covers and store them into its cache.
EDIT: I tried it on my N5. The cover download times didn't improve much, but the 200 milliseconds went to 50.
This performance of around 1.5 covers per second clearly does not match what you are seeing from CalibreCloud, approximately 5 covers per second. My guess is that it is using Dropbox's thumbnail feature, something I cannot do because I need the real cover to insert into CC's database.
As for searching, the reason I am concerned about performance is that for consistency I would need to use the existing CC search engine, which is similar to calibre's. CC's search engine works on 'calibre-processed' information that does not exist in calibre's database (calibre is memory-based). I think that it will take around 250 milliseconds to generate that information for a book, meaning that search will run at around 4 books per second. I have no idea if this is acceptable. I know that it won't be for some number of people.
@Cybmole: thanks for the heads-up on possible problems with Fires. I will try it on mine once I get further along in development.
@Everyone: so far I haven't heard any problems with this feature being dropbox-only. That really would simplify things!