The specific MM4/Magic Node slowness problem has been solved.
The originally reported problem is still there in MM4: once a second PC accesses the same MM DB, MM becomes horribly slow, even after the second PC has stopped.
Regards, Willy

Okay, will do this.
regards, Willy

As usual a debug log would be helpful: http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=69

I checked this with 1418 before I posted the previous post. So unfortunately that doesn't resolve the issue I mean.
There is "something" horribly slow in the combination of tabs/MM4/Magic nodes, also in 1418. Can't put my finger on it, it's definitely not always slow, but would like to know if it's worth the effort to dig into this. Or have others already done so and is it a known issue?
Regards, Willy

1418 should have a fix for multiple tabs and Magic Nodes.

I am using MM4 now on one of our PC's, with the converted library again on the NAS. It seems as if a similar slowdown problem as reported here, does now occur when only this 1 PC is using MM. This slowdown seems to happen when I use Magic Nodes on multiple tabs.

So far it is an impression only. I mean: MM4 does definitely slowdown on some occassions, but I'm not yet sure when this happens exactly.
Note that I mean a slowdown with tens of seconds, or even some minutes.

Is it usefull if I test this more specifically - or is this an already known issue? If you want me to test this: is there any specific information you would want me to provide?

Regards, Willy

Certainly,
I'm counting on you and few others that helped MM become better with each build.

Till then HAPPY MONKEYING!

Thanks for the response.
Let me know if I can do some testing to help (MM3 or MM4).
Regards, Willy

Yes and no, There is SQLite limitation on number of Calls to Library and that is causing the issue We are investigating the way on how to override them and Make MM much faster in Multi Access environments especially in Network access. Which means more testing and testing and testing

Thanks Nohitter, very usefull extension again.

Note that this does NOT solve the initial problem that I started this thread with. Is there any news on that one?

Regards, Willy

willyvds wrote:The reported issue was a long now-playing list at start up, as a cause of slowness. The solution you mention does not remediate that.
My question is: is there a possibility to clean the now playing list automatically when MM shuts down. So: not just remove the already played songs, but also the yet-to-be-played songs.
Regards, Willy

http://www.mediamonkey.com/forum/viewto ... ow+playing

The reported issue was a long now-playing list at start up, as a cause of slowness. The solution you mention does not remediate that.
My question is: is there a possibility to clean the now playing list automatically when MM shuts down. So: not just remove the already played songs, but also the yet-to-be-played songs.
Regards, Willy

willyvds wrote:Lowlander,
could you explain a bit more (or refer to an explanation) what you mean with this auto DJ setting?
I mean what are the possibilities and what is the impact?
I would like to test if this could positively impact our performance.
Regards, Willy

It's fairly self-explanatory. At Options > AutoDJ / Now Playing you can set how many previously played tracks are retained in now playing.

Lowlander,
could you explain a bit more (or refer to an explanation) what you mean with this auto DJ setting?
I mean what are the possibilities and what is the impact?
I would like to test if this could positively impact our performance.
Regards, Willy

And the Auto-DJ options allow you to have MediaMonkey auto-remove tracks from the Now Playing after they have been played.