Quote:
Originally Posted by chaley
I have made a change to verify that the db is still open every time the db is used. This won't slow down the normal case because Android keeps a cache of open databases and gives the cached value back. If the database had been closed, then it will take a bit longer, but this is better than (sometimes silent) death. This change will be in the next CC release, something that should come near the end of the week.
I have also changed some things in when books being sent by calibre are stored into the DB. The existing version starts storing each book when the book arrives, something that works fine if the DB is running at full performance. However, if the DB has slowed down, then this method can make it even slower by having multiple "books" try to access the DB at the same time. It now uses a queue so only one book accesses the db at a time.
|
Thanks chaley. I do seem to notice an improvement in CC functioning since the last DB wipeout happened-- maybe it's my imagination, but rebuilding the DB from scratch seems to have fixed some of the slowness in metadata transfer. The rest of it I guess is likely my phone starting to show its age and RAM limitations with everything I throw at it, though since I did an app cull the poor thing's had more space to breathe. Meanwhile I'll keep logging my calibre sessions; if anything else interesting happens I'll let you know. I wonder if a (semi-)daily log of calibre activity when CC is connected would be of interest to you-- sorta like a daily patient diary?
Looking forward to the new release with upcoming improvements; the on-device library count will hit 10k when I sync it in the morning and probably be at 11k by the next CC release, so I'll be happy to see what the new improvements do then.