Normal for kobo to take forever on "processing content" ? - Page 2

frostschutz · 06-14-2015, 01:05 PM

Make frequent backups of your .kobo/KoboReader.sqlite in any case. Waiting hours for the database to build is bad enough. Having to do it again after a firmware reset or simply due to damaged DB, is mighty annoying.

eschwartz · 06-14-2015, 01:15 PM

I would think that Kobo might want to remove superfluous ToC additions if that might make a significant difference in time processing.

Kobo users tend to be the ones who care more about having lots of books, so a disproportionate number of users would care.

Either way I still think it is silly to lock up the whole UI while waiting for the books to process.

chrisridd · 06-14-2015, 02:27 PM

Thanks for clarifying! Of course Kobo doesn't need to extract the entire [k]epub in memory just to get one or two files, but maybe even that is inefficient.

When I replaced the stdio-based I/O implementation in the Mac epub quicklook plugin with mmap-based I/O I got a nice speedup.

JSWolf · 06-14-2015, 05:53 PM

Quote:

Originally Posted by eschwartz

I would think that Kobo might want to remove superfluous ToC additions if that might make a significant difference in time processing.

Kobo users tend to be the ones who care more about having lots of books, so a disproportionate number of users would care.

Either way I still think it is silly to lock up the whole UI while waiting for the books to process.

It's not just Kobo users. Lots of Sony users wanted lots of eBooks and so do lots of Kindle users.

eschwartz · 06-14-2015, 06:02 PM

Yes there are Kindle users who want lots of books. But there are also lots of Kindle users who don't care.

Kobo specifically targets the users who want lots of books though. (SD card anyone?) Yet they lag behind the Kindle in allowing someone to speedily load their books.

Dunno about Sony -- it is irrelevant, they aren't even supported.

JSWolf · 06-14-2015, 06:46 PM

Quote:

Originally Posted by eschwartz

Yes there are Kindle users who want lots of books. But there are also lots of Kindle users who don't care.

Kobo specifically targets the users who want lots of books though. (SD card anyone?) Yet they lag behind the Kindle in allowing someone to speedily load their books.

Dunno about Sony -- it is irrelevant, they aren't even supported.

Calibre supports Sony very well.

I prefer the Kobo processing than the Kindle processing. At least on a Kobo, you know how far along the processing is. With the Kindle, you have no idea how far along the processing is.

eschwartz · 06-14-2015, 09:11 PM

Quote:

Originally Posted by JSWolf

Calibre supports Sony very well.

I prefer the Kobo processing than the Kindle processing. At least on a Kobo, you know how far along the processing is. With the Kindle, you have no idea how far along the processing is.

Please stop being mendacious. Sony doesn't support the Sonys, therefore there won't be any more firmware upgrades, and potential improvements to the Sony firmware (whether it needs them or not I have no freaking clue) are a non-starter. The fact that calibre supports the Sony as a destination for sending ebook files to is a completely irrelevant concept -- as you well know.

P.S. I love my Kindle, I always know exactly where it is in processing -- DONE!
Kindles process new books extremely fast.

davidfor · 06-14-2015, 09:55 PM

Quote:

Originally Posted by eschwartz

P.S. I love my Kindle, I always know exactly where it is in processing -- DONE!
Kindles process new books extremely fast.

How long would it take if you sideloaded 100 books in one go? Or 1000? Or the 8500 that the OP tried? I'm normally adding a few books at a time, and while I notice the processing screen, it is usually gone before I can disconnect the device.

eschwartz · 06-14-2015, 10:34 PM

I've never tried adding 8500 books at once -- it would probably require more than the 3.5 GB available.

IIRC (it's been a while since I had to load that many books) ~250 takes maybe a minute or *perhaps* two, and books will keep on popping up on the main screen the whole time.

JSWolf · 06-15-2015, 03:10 AM

It is very fast for my H2O to process a few books at a time. But adding 8500 books to an H2O or a Kindle would not be very fast. The processing would be slow. It's not a fault with the devices, it's just because of the sheer volume of books being added in one go.

thp1017 · 06-15-2015, 09:12 AM

I've actually had the H2O *seem* like it is still processing - just copying over a single book, it sat with the status bar at 6% (or some other number, that's just what it showed last night when this happened) for a long time, long past when it should have completed. The first time, when I went to do a hard shutdown via the power button, it immediately switched to sleep and then off. When I started it back up, everything seemed fine.

Next time this happened (its happened a handful of times, probably), I just hit the upper right corner of the screen as if to to open up the settings menu, and the screen screen refreshed just fine, light turned on, and off I went, no problems at all. Not sure what is preventing the screen from refreshing, but it has happened to me on two devices (annoyingly, I had an H2O completely crap out on me about a month back), so it seems firmware related. Hardly the end of the world, once you know

Ripplinger · 06-15-2015, 09:38 AM

When I got the Glo HD, I added slightly over 600 books all at once. It took a little over 20 minutes for the Glo HD to process the contents. Normally I don't add that many at once, but all the same books have been on my Glo so I knew there were no issues with them choking the reader.

Even if I knew all 8500 books had no issues, I would never add that many all at once. I'd break it up into maybe 500 at a time, that way I could recharge it when it drained the battery between book additions.

eschwartz · 06-15-2015, 10:16 AM

Quote:

Originally Posted by JSWolf

It is very fast for my H2O to process a few books at a time. But adding 8500 books to an H2O or a Kindle would not be very fast. The processing would be slow. It's not a fault with the devices, it's just because of the sheer volume of books being added in one go.

And I will say again: the Kindle does not process them slowly, even when you add several hundred books at a time. I have never tested thousands, but I expect it to be no different.

The reason is again as I have already said: the Kindle processes one/a few books, adds them, and repeats. It might also help that I believe metadata is easier to extract from the mobipocket database wrapper than by unpacking an EPUB to get at the OPF. Either way, why does the Kobo slow down the more books you queue and the Kindle doesn't???

JSWolf · 06-15-2015, 11:54 AM

Quote:

Originally Posted by eschwartz

And I will say again: the Kindle does not process them slowly, even when you add several hundred books at a time. I have never tested thousands, but I expect it to be no different.

The reason is again as I have already said: the Kindle processes one/a few books, adds them, and repeats. It might also help that I believe metadata is easier to extract from the mobipocket database wrapper than by unpacking an EPUB to get at the OPF. Either way, why does the Kobo slow down the more books you queue and the Kindle doesn't???

Every Reader that has to process eBooks added to the device will take longer to process the more you add. If you add 200 eBooks, it will take a lot less time than adding 8500 eBooks.

Kobo doesn't slow down. It just takes longer because there are more eBooks to process. Kindles have been known to be slow while processing. So adding 8500 eBooks to a Kindle could very well slow it down. And there is no way a Kindle will not take a long time to process 8500 eBooks.

eschwartz · 06-15-2015, 12:11 PM

Slow down == take longer per book.

Everything clear now? Kthxbai.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Aura HD Stuck at 85% "Processing content" issue	Ken Maltby	Kobo Reader	26	07-07-2013 03:59 PM
Bug in Kobo processing of epub files causing hang in "Processing content"	BensonBear	Kobo Reader	21	12-21-2012 05:47 AM
Recovery from "Processing Content"	mutant_matt	Kobo Reader	8	11-17-2012 07:05 PM
Touch Stuck on "Processing Content" and can't transfer books from Calibre??	Feisty	Kobo Reader	33	01-22-2012 10:15 AM
"Content locked..." with Kobo books - questions	JVM	Kobo Reader	4	04-18-2011 08:58 AM

06-14-2015, 01:05 PM	#16
frostschutz Linux User Posts: 2,282 Karma: 6123806 Join Date: Sep 2010 Location: Heidelberg, Germany Device: none	Make frequent backups of your .kobo/KoboReader.sqlite in any case. Waiting hours for the database to build is bad enough. Having to do it again after a firmware reset or simply due to damaged DB, is mighty annoying.

06-14-2015, 01:15 PM	#17
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	I would think that Kobo might want to remove superfluous ToC additions if that might make a significant difference in time processing. Kobo users tend to be the ones who care more about having lots of books, so a disproportionate number of users would care. Either way I still think it is silly to lock up the whole UI while waiting for the books to process.

06-14-2015, 02:27 PM	#18
chrisridd Guru Posts: 977 Karma: 2209358 Join Date: Nov 2011 Location: London, UK Device: Kobo Aura, Kobo Aura ONE, PocketBook InkPad Color 3	Thanks for clarifying! Of course Kobo doesn't need to extract the entire [k]epub in memory just to get one or two files, but maybe even that is inefficient. When I replaced the stdio-based I/O implementation in the Mac epub quicklook plugin with mmap-based I/O I got a nice speedup.

06-14-2015, 06:02 PM	#20
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	Yes there are Kindle users who want lots of books. But there are also lots of Kindle users who don't care. Kobo specifically targets the users who want lots of books though. (SD card anyone?) Yet they lag behind the Kindle in allowing someone to speedily load their books. Dunno about Sony -- it is irrelevant, they aren't even supported.

06-14-2015, 10:34 PM	#24
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	I've never tried adding 8500 books at once -- it would probably require more than the 3.5 GB available. IIRC (it's been a while since I had to load that many books) ~250 takes maybe a minute or perhaps two, and books will keep on popping up on the main screen the whole time.

06-15-2015, 03:10 AM	#25
JSWolf Resident Curmudgeon Posts: 79,758 Karma: 145864619 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	It is very fast for my H2O to process a few books at a time. But adding 8500 books to an H2O or a Kindle would not be very fast. The processing would be slow. It's not a fault with the devices, it's just because of the sheer volume of books being added in one go.

06-15-2015, 09:12 AM	#26
thp1017 Connoisseur Posts: 82 Karma: 13557 Join Date: Jul 2010 Location: Albuquerque, NM Device: Kobo, KT, KGlo, H2O, Libra	I've actually had the H2O seem like it is still processing - just copying over a single book, it sat with the status bar at 6% (or some other number, that's just what it showed last night when this happened) for a long time, long past when it should have completed. The first time, when I went to do a hard shutdown via the power button, it immediately switched to sleep and then off. When I started it back up, everything seemed fine. Next time this happened (its happened a handful of times, probably), I just hit the upper right corner of the screen as if to to open up the settings menu, and the screen screen refreshed just fine, light turned on, and off I went, no problems at all. Not sure what is preventing the screen from refreshing, but it has happened to me on two devices (annoyingly, I had an H2O completely crap out on me about a month back), so it seems firmware related. Hardly the end of the world, once you know

06-15-2015, 09:38 AM	#27
Ripplinger 350 Hoarder Posts: 3,574 Karma: 8281267 Join Date: Dec 2010 Location: Midwest USA Device: Sony PRS-350, Kobo Glo & Glo HD, PW2	When I got the Glo HD, I added slightly over 600 books all at once. It took a little over 20 minutes for the Glo HD to process the contents. Normally I don't add that many at once, but all the same books have been on my Glo so I knew there were no issues with them choking the reader. Even if I knew all 8500 books had no issues, I would never add that many all at once. I'd break it up into maybe 500 at a time, that way I could recharge it when it drained the battery between book additions.

06-15-2015, 12:11 PM	#30
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	Slow down == take longer per book. Everything clear now? Kthxbai.

Advert

Advert