View Single Post
Old 11-10-2016, 07:14 AM   #14
Steve_Haley
CC iOS Developer
Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.Steve_Haley is no e-book dilettante.
 
Posts: 142
Karma: 53024
Join Date: Jul 2012
Location: England
Device: Variety phones/tablets
Quote:
Originally Posted by Dusky Rose View Post
Is there a limit to how many files the program can handle?[...]
I received an email from someone with the initials M.G. reporting a similar problem. Was that you? If not, could you send me a debug log? It's the last option in the settings menu.

At the moment I don't know what the problem is, but I'll look into it this weekend.

To directly answer the question - the only hard limit for the number of books in the app is about 10 million. In practice though, no device has enough RAM to manage a library of that size. (RAM is different to storage space. It's a bit like how a person can write something down or keep it in their head; normal storage space is writing it down whereas RAM is trying to just remember it.)

Back to the question: we had it working on libraries of about 5,000 books on an original iPad Mini. That's the device with the least amount of RAM that we could get our hands on. It was a bit slow but it coped. Newer devices, like an iPhone 6 or iPad Air were fine. We didn't have a way to see if the old iPad Mini coped with more than that but I wouldn't expect it to have any real problems until we reached more than 10k.

Anyway, send me that debug log and I'll look at it on the weekend.
Steve_Haley is offline   Reply With Quote