View Single Post
Old 10-16-2016, 07:51 AM   #111
rtiangha
Evangelist
rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.rtiangha ought to be getting tired of karma fortunes by now.
 
Posts: 495
Karma: 356531
Join Date: Jul 2016
Location: 'burta, Canada
Device: Kobo Glo HD
Quote:
Originally Posted by davidfor View Post
Ok, I just restarted and opened one of the more complicated PDFs. It took about 30-40 seconds. When I reopen it or most other PDFs, it is only taking a few seconds. But, some of them are still taking 30 seconds or so.

All this suggests there is a process being initialised for PDFs. Why it is taking so long for you is the question. It's probably something to do with the big SD card or the size of the database.
Yeah, I was thinking the same thing. I've noticed that as that database gets bigger, various things just get slower over time, although not by much, just enough to be noticeable. I haven't tried to read a PDF in a while though, which is why this one caught me off guard.

In fact, I can't even compact the database through Calibre anymore as it eventually dies with an I/O error (the last time I tried it I had 2.0 GB free; now I'm down to 1.8). But I can do so using a copy on my hard drive and using an external SQL program, and I just manually copy the result to the card when it's done. I've observed it in progress though and the Wal file never grows larger than 1.7 GB, so it should at least work in theory? But a bigger card with more free space might be helpful.

But unless there's something that can be done on the back end to improve load times, I don't think there's much that can be done, except maybe to reduce the number of items in my library to see if database size is the issue (I'll upgrade to a 128GB card eventually which might help read performance if lack of free space or the fact that my card is almost full is actually the issue, but I won't get my hopes up either). I was thinking of pulling all my PDFs and sticking them in a hidden directory to use with koreader since Calibre can't transfer PDF metadata anyways so maybe this may act as motivation to do so if performance gets any worse. I really do like the Nickel interface though, so we'll see.

Also, for what it's worth, kepubs work just fine; I only have these issues with PDFs, although I haven't tried any other supported file types. And I wasn't able to find any stack logs at all.

Sent from my GT-N5110 using Tapatalk

Last edited by rtiangha; 10-16-2016 at 08:09 AM.
rtiangha is offline   Reply With Quote