Suddenly slow? <CheckForRenamedRecordings>

[dennit]

Suddenly GBPVR was taking several minutes to go from the main menu into either the Recordings or the Video Library. I had just changed the database directly (deleted some channels, renamed, etc. - yes I know I shouldn't do it this way, but it's imposssible for me to do the correct way) and I'd changed some plugins and MDAPI files. I'd also changed my main recording drive (the old one had filled up, and I had a new one that was empty, so I just changed the pointer to the new one).

Replacing gbpvr.db3 did not fix it, so I undid everything with a restore. This did fix it. I then redid each step carefully checking to see if the slow problem reappeared. After all the steps were repeated, it was still working OK ... for about a day, then it was back to incredibly slow to enter Recordings or the Video Library again.

This time I checked the logs carefully and noted that it was taking a minute and a half after I requested it to show the Recordings to do the "/CheckForRenamedRecordings" steps. There were over 300 of these entries (only two shown below):

Code:

2009-03-27 21:38:22.933    VERBOSE    [1]    loadRecordings():1
2009-03-27 21:38:22.933    VERBOSE    [1]    RecordingFactory.loadSchedule()
2009-03-27 21:38:22.933    VERBOSE    [1]    getValue cached value: /settings/AutoRemoveMissingRecordings : false
2009-03-27 21:38:22.933    VERBOSE    [1]    getValue cached value: /settings/CheckForRenamedRecordings : true
2009-03-27 21:39:35.486    VERBOSE    [1]    getValue cached value: /settings/CheckForRenamedRecordings : true

I changed config.xml to:
<CheckForRenamedRecordings>false</CheckForRenamedRecordings>
and this solved it. Suddenly I'm fast again - a second or two to enter what had taken minutes.

So my question: What does this do? Is it OK to leave it set to false? Why did I go from fast to slow, but not immediately? Is it related to the change of the recording drive?

Thanks for any info.

[sub]

Do you record to the c:\ drive or somewhere else?

[dennit]

Do you record to the c:\ drive or somewhere else?

I previously recorded to H: and changed it to an empty E:

[sub]

Are these physical drives in that machine (fast), or (slow) network or USB drives?

[dennit]

Are these physical drives in that machine (fast), or (slow) network or USB drives?

Direct attached storage physical drives - they are quite fast - I tested them just after installation.

[sub]

Sorry, I dont know. We've only ever seen a problem with that setting on slow drives in the past. If you're not transcoding, you can set it to false.

[dennit]

Sorry, I dont know. We've only ever seen a problem with that setting on slow drives in the past. If you're not transcoding, you can set it to false.

Thanks. I'm not transcoding, so I'm free to leave it off. Can you give me a brief summary of what it's doing at this point? Is it checking each file listed in the recordings part of the database?

As I type this, I recall that I have some files in the recordings database that were imported and reside on another networked drive. They've been there for a year or so, but I did have some trouble with the network connection to that drive for a while. Perhaps that explains why switching to an old gbpvr.db3 didn't fix it - those files would have been in the old db3.

Hold on while I check it ....

AHA! It appears that the network link was down or slow when I had the problems. I verified the network link is now good, and reset <CheckForRenamedRecordings> back to true, and it works fine.

[sub]

AHA! It appears that the network link was down or slow when I had the problems. I verified the network link is now good, and reset <CheckForRenamedRecordings> back to true, and it works fine.

Great.