View Issue Details

IDProjectCategoryView StatusLast Update
0004430MMW v4Synchronizationpublic2008-03-21 14:42
ReporterLudek Assigned To 
PriorityimmediateSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version3.0 
Fixed in Version3.0 
Summary0004430: Regression: Initialization of device config dialog can take too long
DescriptionInitialization of device config dialog can take too long to show up the dialog due to query optimization.
Additional InformationReported by Drathus at
http://www.mediamonkey.com/forum/viewtopic.php?t=24816
TagsNo tags attached.
Fixed in build1146

Activities

Ludek

2008-03-01 02:38

developer   ~0013215

Fixed in build 1141.

Ludek

2008-03-01 13:15

developer   ~0013216

Further optimization based on various purposes - tested on the Drathus DB (http://www.drathus.com/MM.DB)

Fixed in build 1141.

peke

2008-03-08 01:02

developer   ~0013254

Verified 1141

It still Takes 4-7 Secs to Init but it is much improved from 1140 which take 20-30 Sec to init.

rusty

2008-03-20 19:49

administrator   ~0013426

Ludek, in build 1144, it takes about 5 seconds for this dialog to open on my machine. I never saw this delay in previous builds. Can you verify whether this is really fixed as intended?

Ludek

2008-03-20 20:18

developer   ~0013428

Yes, if you use the Drathus DB it takes about 4-5 seconds, but this is much better than before when it taken 30 minutes.

Or If you think that it is slower directly on your DB then it is strange and generate a debug log using DebugView and attach.
It still takes about 2 seconds on my DB ( 10k tracks).

rusty

2008-03-21 03:47

administrator   ~0013431

I have a db of 6500 tracks and it takes ~4.5 seconds to open the Sync Options dialog on my machine with build 1144.

To open the same dialog on MM 3.02 takes ~1 second.

I'm posting the db (mm.zip) + a debug log that shows what happens when I open the Sync dialog to the ftp server.

Ludek

2008-03-21 11:06

developer   ~0013438

Last edited: 2008-03-21 11:15

Rusty, Thank you!

I found that it was related to podcasts. One podcasts query has not been optimized and it caused the problem in the whole query.

Problem was that neither I xor Drathus didn't have so much podcast episodes as you.

Fixed in build 1146. It takes a half of second now ;-)

Btw.
During the last three weeks I opimized about 100 SQL queries around the app. so MM 3.0.3 will be much more faster mainly on large DBs. (On some DBs MM 3.0.2 is unusable in some ways)

rusty

2008-03-21 14:42

administrator   ~0013441

Verified 1146.