View Single Post
Old 10-22-2011, 01:17 PM   #592
Micah
Bluefire Reader dude
Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.
 
Posts: 329
Karma: 1089156
Join Date: Oct 2010
Location: Seattle
Device: Ipad
Quote:
Originally Posted by kyteflyer View Post
Is there a max number of books that Bluefire can handle?

I am using a 3GS 32G and it really struggles to get going. When I had put 80 books in (dragged over via finder/itunes) it just wouldnt open. Well, that is, I became impatient after about 5 minutes and stopped it. I deleted via Phoneview, and have now just dragged in 12 which also took ages to open, but seems OK now. Adding one or two at a time doesnt seem too stressful.

Whats the max it can handle in its database?
There is not an "actual" limit, though collection in excess of a few hundred can get unwieldy. Especially when initially sideloading lots of books - where the app can take a *long* time to rebuild the library and the entire app will run very slow until it completes (there's a lot going on in the background when books are added to the library - in large part in order to provide the Library Lending features/DRM). Also, the app generates cover art from taking a snapshot of the first page of each book. When we added Retina resolution support to that feature, oy! it slowed way down. Working on that.

I've considered enforcing an arbitrary limit, just to avoid people hating on us for that slow library build, and related performance issues with large libraries. But, as the devices get faster, it is less of an issue, and seems wrong to limit it across the board.

Maybe we just need better ways to communicate with users telling them while we are working in the background to build the library, and maybe we need to have some kind of "alert" for large libraries informing users they might want to consider archiving some of the titles for better performance?
Micah is offline   Reply With Quote