INTERACT FORUM

More => Old Versions => JRiver Media Center 23 for Linux => Topic started by: BryanC on March 27, 2018, 05:07:52 pm

Title: Why is the save cover art to external location so resource intensive?
Post by: BryanC on March 27, 2018, 05:07:52 pm

I have about 4000 albums and saving the cover art to a new external location (on a fast SSD) has taken about an hour thus far. Meanwhile, MC is hung and consuming 100% of one of my cores. I am watching the .jpg count increase in my external directory at the rate of about 1 cover art file per 5 seconds. For a total file operation of less than 1GB, it shouldn't take this long.

Title: Re: Why is the save cover art to external location so resource intensive?
Post by: BryanC on March 29, 2018, 12:43:56 pm

I was using beta 24.0.7 and thus this may have been caused by this migration issue:

24.0.8 (3/29/2018)
2. Fixed: Copying Cover Art folder from MC23 to MC24 during upgrade installation did not work.

It's possible that it was pulling from the tags or something.

Title: Re: Why is the save cover art to external location so resource intensive?
Post by: Hendrik on March 30, 2018, 11:47:57 am

That only refers to the installer, which is only used on Windows, not a task MC itself actually does.

Title: Re: Why is the save cover art to external location so resource intensive?
Post by: bob on April 03, 2018, 10:18:23 am

Quote from: BryanC on March 27, 2018, 05:07:52 pm

I have about 4000 albums and saving the cover art to a new external location (on a fast SSD) has taken about an hour thus far. Meanwhile, MC is hung and consuming 100% of one of my cores. I am watching the .jpg count increase in my external directory at the rate of about 1 cover art file per 5 seconds. For a total file operation of less than 1GB, it shouldn't take this long.

That's brutal. Sounds to me like it's doing a byte by byte copy.
What filesystem is on the external location?
Is that location part of auto-import?

Title: Re: Why is the save cover art to external location so resource intensive?
Post by: BryanC on April 03, 2018, 01:13:20 pm

Cover art directory is ext4 and that specific directory is not part of auto-import. I ended up choosing to store the cover art alongside each album instead of a single cover art directory because I experienced this same issue on my subsequent machines.

Title: Re: Why is the save cover art to external location so resource intensive?
Post by: bob on April 03, 2018, 02:40:43 pm

Quote from: BryanC on April 03, 2018, 01:13:20 pm

Cover art directory is ext4 and that specific directory is not part of auto-import. I ended up choosing to store the cover art alongside each album instead of a single cover art directory because I experienced this same issue on my subsequent machines.

Is it a sub directory of the auto-import? The reason I ask is that I'm trying to figure out if our use of the linux filesystem notifiy might be causing the issue.

Title: Re: Why is the save cover art to external location so resource intensive?
Post by: BryanC on April 10, 2018, 11:04:05 am

No, it's not a subdirectory of any of my auto-import folders, although it resides on the same disk in the same parent directory, i.e.:

Auto-import:
/run/media/user/Media/Music
/run/media/user/Media/TV
/run/media/user/Media/Moves

Cover art dir:
/run/media/user/Media/Covers

Title: Re: Why is the save cover art to external location so resource intensive?
Post by: bob on April 12, 2018, 09:00:34 am

Quote from: BryanC on April 10, 2018, 11:04:05 am

No, it's not a subdirectory of any of my auto-import folders, although it resides on the same disk in the same parent directory, i.e.:

Auto-import:
/run/media/user/Media/Music
/run/media/user/Media/TV
/run/media/user/Media/Moves

Cover art dir:
/run/media/user/Media/Covers

If you run
sudo dmesg
from a terminal windows when you are trying to move the cover art do you see any hardware errors?