Does Forma become slower in managing its stored library with more ePubs in storage

droopy · 02-28-2019, 05:20 PM

I'm considering getting a Kobo Forma, maybe just the smaller, 8GB version.

Can anyone tell me if managing your libary of books on your internal storage slows down the more ePubs you have? What, for instance, is the difference in speed, when viewing your library, between having 100 ePubs (let's say it's 100MB) versus 8,000 (let's say that's maxing out the 8GM storage)?

What prompts my question is a comment I saw on an ereader blog. Please refer to the comment posted by fjtorres on September 5 2013

Quote:

I hear similar complaints about the Sonys on mobileread.
The database limit (~2000 books) seems to be due to the hardware, onboard memory for caching the metadata, perhaps. The only readers that seem to be able to manage large libraries on SD card are the ones that use the file system instead of a database. Which explains why 2GB on board storage has become so common; it keeps the library within manageable bounds–reducing support calls–and reducing build costs.

NiLuJe · 03-01-2019, 04:54 AM

Navigating the library will slow down, as in nearly every reader out there. Search should still be pretty snappy, though. And it works very well, that's mainly how I browse my library, via search.

Mercador · 03-01-2019, 09:19 AM

My hypothesis is the way the navigation works. It's an index within an array and the bigger the array, more work is needed by the CPU to move the index from A to Z. However, that's really basic code so it shouldn't slow down the reader like that.

My second hypothesis is that for every book within the index, the reader have to fetch the information from the memory for EVERY book within the listing showed. That would explain why more data on the memory, more data is fragmented, slower it gets.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Sideloaded Epubs on Forma	disconnected	Devices	12	10-26-2018 01:36 AM
Notes & Highlights for epubs stored on the sd card	einkuser	Barnes & Noble NOOK	0	07-19-2014 09:49 PM
Some slower operations don't respect Virtual Library Restrictions?	Sidetrack	Library Management	4	09-08-2013 10:50 PM
Where are the books and annotations in library stored?	henry_moh	enTourage Archive	4	10-07-2010 02:10 PM
Anyone find Reader Library 3.1 to be slower than ****?	sayhello	Sony Reader	5	12-30-2009 11:03 AM

03-01-2019, 04:54 AM	#2
NiLuJe BLAM! Posts: 13,496 Karma: 26047188 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Navigating the library will slow down, as in nearly every reader out there. Search should still be pretty snappy, though. And it works very well, that's mainly how I browse my library, via search.

03-01-2019, 09:19 AM	#3
Mercador I'm not a number! Posts: 244 Karma: 11496 Join Date: Jul 2011 Location: Quebec City Device: Kobo Elipsa	My hypothesis is the way the navigation works. It's an index within an array and the bigger the array, more work is needed by the CPU to move the index from A to Z. However, that's really basic code so it shouldn't slow down the reader like that. My second hypothesis is that for every book within the index, the reader have to fetch the information from the memory for EVERY book within the listing showed. That would explain why more data on the memory, more data is fragmented, slower it gets.

Advert