CPU load when deleting physically folder mapped as library

You have a question or need an advice about how to do something? Ask it here!
Post Reply
Farbo
Posts: 346
Joined: 11 Apr 2012 15:04

CPU load when deleting physically folder mapped as library

Post by Farbo » 12 Apr 2012 10:49

Hi Bernd.

When PF is running and I make physical changes to folder based libraries through windows explorer (like clearing one folder and deleting it) PF suddenly starts to consume around 90-95% of CPU. I understand it could cause a problem if I delete physically folder which is mapped as library but anyway, if this is a bug, could you have a look at it?

Thank you.
Peter

Farbo
Posts: 346
Joined: 11 Apr 2012 15:04

Re: CPU load when deleting physically folder mapped as libra

Post by Farbo » 12 Apr 2012 15:04

So the workaround would be:

1. move tracks from that directory to another desired
2. after folder is empty delete this library from libraries (in settings)
3. delete folder physically

Right?
Peter

User avatar
radio42
Site Admin
Posts: 5574
Joined: 05 Apr 2012 16:26

Re: CPU load when deleting physically folder mapped as libra

Post by radio42 » 12 Apr 2012 15:11

Yes, or more simple:
Turn off the 'Auto Watch' option for the moment you are doing such heavy delete/rename/copy folder operations on your folder-based media lib...
and when done perform a 'Rescan' for that media lib and turn 'Auto Watch' back on again.

User avatar
radio42
Site Admin
Posts: 5574
Joined: 05 Apr 2012 16:26

Re: CPU load when deleting physically folder mapped as libra

Post by radio42 » 12 Apr 2012 21:37

Sounds like this is NOT a bug, but rather a feature you have selected within ProppFrexx.
I assume you have the 'Auto Watch' option selected with such folder based media library.
In such case the Windows operating system reports all changes to that 'monitored' folder (incl. all changes to any sub-folder or files within any sub-folder) to ProppFrexx.
This in order to let ProppFrexx know about these changes and make appropriate changes directly within its related media library.

As outlines in the docs, this is might be (depending on your changes and your underlying hardware) a quite heavy operation (both from an I/O as well as an CPU point of view - note that heavy I/O operations also use CPU resources).

So I guess what you are observing is just this.

Post Reply

Who is online

Users browsing this forum: No registered users and 5 guests