0011185: Wi-Fi Sync: analysis takes much too long, and tracks sync needlessly (regression) - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0011185	MMA	Synchronization	public	2013-08-22 21:23	2013-08-29 18:24

Reporter	rusty	Assigned To
Priority	immediate	Severity	major	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	1.0.4
Target Version	1.0.4	Fixed in Version	1.0.4

Summary	0011185: Wi-Fi Sync: analysis takes much too long, and tracks sync needlessly (regression)
Description	When attempting to sync mma 1.0.4.0158 against MMW 4.1.1654, the Analyzing sync list... phase took ~20+ minutes (the device has around 3000 tracks). Note that prior to Wi-Fi synchronization, I'd performed a wired sync (just a couple of tracks synced), after which I deleted 3 0B .pla files from the internal /Playlists directory (leaving 2 remaining .m3u playlists on the external /Playlists directory), so as to prevent 0010166 from occurring. Then I immediately initiated the Wi-Fi Sync. --> the analysis phase took ~20 minutes! In addition, 600 tracks started to sync, when none should have synced (as described above, a wired sync performed just beforehand synced just a couple of tracks)! MMW Debug log is posted to the ftp server.
Tags	No tags attached.

Fixed in build	159

peke 2013-08-22 23:07 developer ~0037242	I wonder could that be regression from changes in 0011127 ?

rusty 2013-08-23 02:15 administrator ~0037243	I tested a clean install of MMA on a Nexus 7 and found that: - Initial wifi sync of 2 playlists, an Album, and an audiobook worked fine - Subsequent wifi sync --> playlists were resynced, and duplicated on the device (similar to 0011017, except this time the bug occurs even when both sync operations are over wifi).

Ludek 2013-08-23 09:38 developer ~0037245 Last edited: 2013-08-23 09:52	BTW: I analyzed the MMW's debug log attached on FTP and I see that MMA analyzes/reads the sync-list slower (5 tracks per second), but my speculation is that it was cased by deleting mmstore.db here 0010166:0037239 and thus MMA needed to pair all the tracks again? And the 600 tracks started to sync again, but these tracks needed auto-conversion and because you deleted mmstore.db, MMA couldn't know the auto-convert hash (media.ac_media_hash) and thus MMA thinks that auto-convert rules has been changed for the tracks and re-downloaded them.

marek 2013-08-23 12:41 developer ~0037247	Optimized in build 159 The main part of the sync time was the pairing. I've optimized current pairing process as much as possible (10 tracks per seconds). Next sync will be certainly quick because all media are already paired. But generally, the process flow was ok.

marek 2013-08-24 12:18 developer ~0037252	Yes, it should be fixed, BUT now we identify playlist by it's new guid and path, so it is possible to have more playlists with same name (as in MMW). If you have playlist with same name (and different path) in mediastore, it is possible to see "duplicates". It is possible that you have some old (from previous build) but valid playlist in mediastore with same name and different path. If you still observe this issue, please post here your mmstore.db to verify it.

peke 2013-08-26 23:36 developer ~0037283	Looks like initial Pairing took some time but for testing purposes I have used LG L5 (Reset to factory defaults and upgraded to JB 4.1.2) where if MMA 159 and MMW 1654 used as only app to sync analyze of 3738 Tracks (6736 MB), 17 Playlists took approximate 2 Min, Transfer of tracks took around 47min WiFi[Avg. 2.58 MBps], 25 min USB [avg. 5.76 MBps] Sony Tipo (Had 500-600 tracks) sync. 2145 Tracks (3891 MB): Analyze 4 Min., WiFi 36 Min. [avg. 1.94 MBps], USB 21 min. [avg. 3.6 MBps] That was average test sunc on three times Resync on both devices and clean MMA Install, after phones Soft reset and initial Media Scan finish to maximize free memory. I had big problems twice with MMA closing due the low memory Unless I firstly start playback from MMA Widget -> Opem Full MMA and init sync. Will update 0011195 with findings.

rusty 2013-08-29 18:24 administrator ~0037354	Verified 161. Analysis is still not speedy (e.g. ~5 minutes), but it's much better than previously; and no duplicates.