[1460+] MM4 performance with large library sucks

[robojock]

one step forward three steps back had to cancel the scanning of the library after 13 hours and it was not finished...

1. Scanning library 13+ hours
2. Opening a node 2+ minutes
3. Right Click find from the same 2+ minutes

Performance with mm4 on large library painful!

[Lowlander]

1391 will have node opening improvement: http://www.ventismedia.com/mantis/view.php?id=7843

[chrisjj]

I would expect the grid to be updated on each song.

That would be crippling. I'd expect it to be updated only on each Add/Rescanned song in view.

[Lowlander]

I'd expect it to be updated only on each Add/Rescanned song in view.

Of course, no need to update grid for songs not in grid unless new songs belong in list.

[robojock]

FIXED!!!

Thank you to all developers!

[robojock]

Im happy with mm4 performance, just noticed a little issue that maybe you devs can fix? On my library if i open the properties (shift+enter or right click) to tag files it feels like it takes longer than mm3 to open, waiting time about about 2-3 seconds. While in the same window jumping from one song to the next (alt+arrow key) also feels longer than mm3, waiting time about 2-3 seconds.

[rusty]

Robojock,

Thanks. Tracked here: http://www.ventismedia.com/mantis/view.php?id=8101

-Rusty

[robojock]

Fixed in 1404 Thanks!

[robojock]

Rusty there seems to be a regression with build 1408 scanning the library, it scans a few files pauses, scans a few more files and pauses.

[rusty]

Robojock,

I tested 1407 vs 1415 and 1415 was slightly faster at scanning. Are you still experiencing a problem?

-Rusty

[robojock]

Robojock,

I tested 1407 vs 1415 and 1415 was slightly faster at scanning. Are you still experiencing a problem?

-Rusty

No rusty i am not experiencing that problem anymore with build 1415, thanks!

[lcloss]

I have a MP3 database larger than 800 GB.
The MM.db file is around 350MB, and I´m also having some slowness that I wouldn´t expect.
I´m using MM 4.0.0.1459
My worst problem appears when changing from songs. If I start to play a song, and hit NEXT, no problem.
If I start a song and hit another one (not on the same sequence) the MM holds for about 4 seconds for no good reason.
Would appreciate to understand why.

[nohitter151]

I have a MP3 database larger than 800 GB.
The MM.db file is around 350MB, and I´m also having some slowness that I wouldn´t expect.
I´m using MM 4.0.0.1459
My worst problem appears when changing from songs. If I start to play a song, and hit NEXT, no problem.
If I start a song and hit another one (not on the same sequence) the MM holds for about 4 seconds for no good reason.
Would appreciate to understand why.

Since you seem to be experiencing an issue that is different from the one reported in this thread could you please:
1. Upgrade to build 1460 (beta build)
2. Confirm the problem still occurs
3. If so, generate a debug log
4. Submit a new topic with a thorough description and said debug log
Thanks!

[Ludek]

Does this happen also if you close the Art & Details window?

[robojock]

*update* performance with build 1459 was good, few issues still.

1. once the scanning has completed it creates a report of how many files it scanned, how many were updated and how long it took, while mm is busy with in the background on my collection it becomes "unusable" until the report has completed which can take a few minutes. <---- isn't mm supposed to use more than one core? (I have 4 with 4gigs of ram)

2. right clicking and doing a search of same artist/album makes stalls mm for a bit, although doing a search via the search bar is very very fast but please look into the right clicking part because that is a feature i use alot.

*update* build 1460 and 1461... devs did something there because i have a regression now on scanning it scans a bit pauses then continues for a few files and pauses, if i remember correctly it would take about 5-6hours to do a full scan on my system (that is starting from scratch now, new database)

If you compare the following image to my previous images you'll see there is a regression on the scanning, i stopped the scanning because i saw it was taking to long and it was only half way.