CC V3.4.2 has been published - Page 2

chaley · 08-10-2014, 08:53 AM

Quote:

Originally Posted by HarryT

Hi chaley,

I've no idea why, but today my T68 has started behaving itself again. Tabs in the grouping drawer are opening after a delay of about 4s, which is acceptable given the size of my library (currently 3560 books on the T68). All very strange - I'll keep an eye on it and send you a debug log if it starts misbehaving again.

Glad to hear it is working better. That said, 4 seconds seems long. Perhaps there is some app running in the background?

My 2 year old Galaxy Nexus was running very slowly, to the point where it would take over almost 2 seconds to exit an app and show the launcher. The back key in Chrome stopped working. Etc. After spending some days trying to work out why it was unhappy, I gave up and factory reset it, reinstalling all the apps. Now it works fine, very snappy. Conclusion: something in these devices can get confused and tired, and it isn't at all easy to find and fix it.

HarryT · 08-10-2014, 12:48 PM

It's misbehaving again. I've emailed you the debug log.

chaley · 08-10-2014, 03:28 PM

Quote:

Originally Posted by HarryT

It's misbehaving again. I've emailed you the debug log.

I have looked over the debug log and it really appears that there is some background task running on your device from time to time. What I see is:

Using 3.4.1: the database times to open the grouping drawer average around 6 seconds. There were not many of these samples in the debug log.
Using 3.4.2 on the 9th: at noon, the average was around 6 seconds. At 17h there are several in excess of 25 seconds, then 4 with an average of 6 seconds. At 18:30 we jump up to an average of nearly 25 seconds, but several are at 6 seconds. At 19:30 there are several at 6 seconds, jumps up in excess of 20 seconds, then falls back to 6 seconds.
On the 10th at noon we are back to 6 seconds. At 17:35 we are still at 6 seconds. At 17:40 we see 13 seconds and 21 seconds, with an average of around 18 seconds.

What this says is that a) V3.4.1 and V3.4.2 aren't that different, and b) the same version of CC is seeing wildly database access different times. The only reason I can see for this is that something else on your phone comes to life from time to time, consuming memory. Do you have any cloud sync programs or other background apps running?

It is possible, perhaps even probable, that the database created by an upgrade is not as efficient as one created from scratch. In particular, 3.4.1 added a column to the main database table, and I doubt that Android's database manager would do that operation in an optimal fashion. What I leading to is that it might be a good idea to uninstall CC, reinstall it, and then resend the books. This would create a database where all the storage for a given row is together. I totally understand why you might not want to do such an operation, but it might help.

Other than looking for background tasks and rebuilding the database, I don't have any suggestions. Sometimes CC database ops are fast(er) and sometimes they are not, and I am not sure what I can do about that.

Ahhh: one idea: if you are using user-defined sorts then sort by title, then author, then title. That will reinitialize the sorts to something basic, simplifying the database queries. If that helps then I have an idea of something I can do.

HarryT · 08-10-2014, 04:20 PM

Thanks, chaley. Could I leave all the books on the device, uninstall CC, then reinstall and do a "scan on initial connection"? Would that be quicker than re-sending all the books again?

I don't have anything else running on the T68 that I'm aware of. I just boot it, then start CC. WiFi is turned off.

chaley · 08-10-2014, 04:32 PM

Quote:

Originally Posted by HarryT

Thanks, chaley. Could I leave all the books on the device, uninstall CC, then reinstall and do a "scan on initial connection"? Would that be quicker than re-sending all the books again?

I don't have anything else running on the T68 that I'm aware of. I just boot it, then start CC. WiFi is turned off.

This will be much faster if most of the books are epub. If they are other formats, then no because CC must send the all the books back to calibre for analysis.

Be sure to do a backup/restore of your settings.

HarryT · 08-10-2014, 04:33 PM

All my books are ePub

. Thanks - I'll give it a go tomorrow and let you know the outcome.

kaufman · 08-10-2014, 05:03 PM

I was having a similar problem last week and a full uninstal/reinstall fixed me right up.

HarryT · 08-11-2014, 06:17 AM

OK, looks like it's fixed. Uninstalled and reinstalled. Took a couple of hours to do the initial sync with Calibre, but now grouping nodes open in under a second! So it does appear to have been an issue caused by the database upgrade, rather than something else running on the device.

chaley · 08-11-2014, 06:55 AM

Quote:

Originally Posted by HarryT

OK, looks like it's fixed. Uninstalled and reinstalled. Took a couple of hours to do the initial sync with Calibre, but now grouping nodes open in under a second! So it does appear to have been an issue caused by the database upgrade, rather than something else running on the device.

OK, that is two people who had this problem. Seems like it is time for me to start looking for a solid explanation.

Thanks for your patience and your feedback.

HarryT · 08-11-2014, 07:17 AM

Quote:

Originally Posted by chaley

OK, that is two people who had this problem. Seems like it is time for me to start looking for a solid explanation.

Thanks for your patience and your feedback.

Thank you for the help from you and kaufman. I'm just happy that it's fixed

. Going from 25s to 1s for a database lookup is something of an improvement!

chaley · 08-11-2014, 07:19 AM

Quote:

Originally Posted by HarryT

Thank you for the help from you and kaufman. I'm just happy that it's fixed

. Going from 25s to 1s for a database lookup is something of an improvement!

Could I trouble you to do a database clean and then send me a debug log? That will tell me the size of the db compared to what it was before you rebuilt it. No problem if you don't have the time or energy.

HarryT · 08-11-2014, 07:45 AM

Database cleaned and new debug log sent, as requested.

chaley · 08-11-2014, 07:52 AM

Quote:

Originally Posted by HarryT

Database cleaned and new debug log sent, as requested.

Well, the old and the new database are the same size within 1%, so one theory down the drain. There really is only one possibility left: the internal structure of the tables is not changed (compacted) by the clean. I will look for evidence of this.

Thanks again.

HarryT · 08-11-2014, 07:55 AM

Quote:

Originally Posted by chaley

Well, the old and the new database are the same size within 1%, so one theory down the drain. There really is only one possibility left: the internal structure of the tables is not changed (compacted) by the clean. I will look for evidence of this.

Thanks again.

Thank you!

What's the debug log showing as the current database response times, BTW? A couple of seconds?

chaley · 08-11-2014, 08:04 AM

Quote:

Originally Posted by HarryT

What's the debug log showing as the current database response times, BTW? A couple of seconds?

For 15 samples, the average time in the DB when you open the grouping drawer is .9 seconds. The max is 1.1 seconds, and the min is .25 seconds. The visible time will be longer because of the screen layout and graphics work necessary.

So yes, a very real improvement.

And no, I don't understand the huge variation in times. Perhaps the DB is doing some of its own maintenance?

08-11-2014, 06:17 AM	#23
HarryT eBook Enthusiast Posts: 85,556 Karma: 93980341 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	OK, looks like it's fixed. Uninstalled and reinstalled. Took a couple of hours to do the initial sync with Calibre, but now grouping nodes open in under a second! So it does appear to have been an issue caused by the database upgrade, rather than something else running on the device. Last edited by HarryT; 08-11-2014 at 06:44 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
First published book	AppleTree13	Self-Promotions by Authors and Publishers	0	10-04-2013 07:36 AM
Published - Dates	bigbird1227	Plugins	4	08-21-2011 06:54 AM
'Published date' and 'originally published date'	Arrghus	Calibre	2	07-29-2011 12:43 AM
Published Dates	bigbird1227	Library Management	7	06-10-2011 10:40 AM
Date published	philandjan	Library Management	1	06-02-2011 11:43 AM

08-10-2014, 12:48 PM	#17
HarryT eBook Enthusiast Posts: 85,556 Karma: 93980341 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	It's misbehaving again. I've emailed you the debug log.

08-10-2014, 04:20 PM	#19
HarryT eBook Enthusiast Posts: 85,556 Karma: 93980341 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	Thanks, chaley. Could I leave all the books on the device, uninstall CC, then reinstall and do a "scan on initial connection"? Would that be quicker than re-sending all the books again? I don't have anything else running on the T68 that I'm aware of. I just boot it, then start CC. WiFi is turned off.

08-10-2014, 04:33 PM	#21
HarryT eBook Enthusiast Posts: 85,556 Karma: 93980341 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	All my books are ePub . Thanks - I'll give it a go tomorrow and let you know the outcome.

08-10-2014, 05:03 PM	#22
kaufman Calibre Companion Fanatic Posts: 873 Karma: 1088610 Join Date: Nov 2006 Device: Galaxy Note 4, Kindle Voyage	I was having a similar problem last week and a full uninstal/reinstall fixed me right up.

08-11-2014, 07:45 AM	#27
HarryT eBook Enthusiast Posts: 85,556 Karma: 93980341 Join Date: Nov 2006 Location: UK Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6	Database cleaned and new debug log sent, as requested.

Advert

Advert