MediaMonkey forum

MM 1353 should improve this.

@ Devs thumbs up with the scanning!! It definitely much faster now Thanks

One of my other issues is still a problem, clicking on of of the nodes (and sub nodes) under music->location-> C:/D: etc. makes me wait for a few seconds making mm unusable for that time until that node has expanded.

Expanding nodes is in general a little slow, but you're right, especially the location one.

We are looking for better Handling of location nodes. Firstly we have made things show in Real-time Fast and as number of tracks rise maintaining real-time and sorting proved difficult. We are investigating what and how things can improve without losing functionality/usage we all used too.

peke windows / ms, has made some updates that cause realtime running of programs to be very slow, not sure what they did, but i'm getting faster times for programs running and or loading by using either above normal or normal prioritys anything higher is taking a chance if it is going to be what the setting is or slower then normal..

maybe that is messing with the nodes?

Location node is extremely slow and can cause MediaMonkey to hang all together here. Video node seems to be improved as pre-1355 it would hang a minute + as well on expanding.

Hi all, thanks for carrying on the topic/

Guess i'm no power user since i never had a clue about changing node while updating !

I reverted to MM3 and rescanned the 100k collection, in whatever node (most likely lib location) including 7k new entries. Took like 2hours. I don't notice any performance problem with mm3 on a i7/xp combo.

OTOH MM4 will have a hard time attracting users, even more so new ones if it ships as is, performance wise. Just my .02€...

Pardon my insisting on it, having posted several times about that, but making db file contiguous on drive has HUGE impact on overall experience. That works for MM3 as well as MM4. Here I'm talking overall browsing experience, not just scans and updates. Makes the thing so smooth you won't suspect a 100k collection. I mean WMP is slower with 1k ... The improvement is even more obvious with album arts on.

Wouldn't MM4 be a good time to look at db fragmentation ? Shouldn't be that hard to preallocate some space and prevent sparsing. NTFS has all windows needs for this. Not that it would make a difference here : my audio and db drive is vfat Maybe I'd put the db on an ntfs drive, then.

I'll wait until next release to reinstall and build a new db. Will keep an eye on performance. Thanks for the tip on node picking. Something tells me a LOT of "power users" would wish it was documented in plain sight somewhere

Rojer.

Yes, the location node is way too slow. I checked the sql used and tweaked it a bit, making it twice as fast.
I also have some other ideas how to make it faster. I'll notify the devs with my findings

Location node can take 2+ minutes on a clean install in the Video collection with 5 files in 1 folder.

I've stopped using mm4 for now, the speed of doing certain tasks is driving me crazy

i am really disappointed with mm4 performance and at the moment it doesn't feel as if it is going to get better

with build 1361 location node feels a bit faster than previous builds, but scanning has gone backwards, it is slow again i cancelled my scanning after 7+ hours and it still wasn't finished, actually it was far from finished.... Right clicking a song and doing a search for the "same" lets mm hang for a bit, opening the tag window takes a few seconds before mm opens it up... Its all these small things that mm4 unusable for me, i stopped testing previous builds cause of that, with this build i decided to give it a try... what a disappointment.

Yeah these things definitely need improvement BUT MM3 was slow at those things too so I don't expect MM4 to be any better than MM3 considering the added functionalities.

Lowlander wrote:Location node can take 2+ minutes on a clean install in the Video collection with 5 files in 1 folder.

~2000 videos in 200 folders, -some with hundreds of videos-, and the speed feels absolutely normal; probably the same as with music.

Build 1362 is going to include additional performance improvements. Right now MM looks up an image everytime you select a file which _really_ slows things down with a video collection if it's stored on the network.

Also, keep in mind that you're using debug builds which are slower by nature. Once we get to the RC stage, we'll start creating 'normal' builds which will be faster.

-Rusty

Still no improvement here on my side at the moment im running mm3 for my music and mm4 portable just for my videos.

Would it be possible to have in future maybe 2 databases? One just for audio part and one for video? Is that too complicated? I am really trying my best to help the devs to solve the problem, running mm4 now with just a few files is fantastic but if i start to add my whole collection of music and movies it starts to slow down as hell