Thank You Vacuum

[sagean 0]

Just wanted to post to say thank you for the vacuum feature. I as a layperson have no idea what it does or how it works, however, I have been stuck on running 4.6.4.0 as any newer version would freeze and corrupt recordings; The vacuum has resolved my problems and allowed me to upgrade.

I recently saw an update for 4.7.0.60 and then shortly after 4.7.1.0 and upgraded to those.  Unfortunately I again started experiencing issues with the server becoming unresponsive and the DVR dumping out a lot of corrupted files so I reverted again to 4.6.4.0.  While I had 4.7.x I noticed a feature called vacuum but didn't use it due the message saying it could take forever and no real way to monitor it. Later I figured that I'd give it a shot because what do I have to lose and was unable to find the feature in 4.6.4.0 (didn't realize it was added to 4.7) but found an old forum thread about how to perform the vacuum by modifying the server xml file. I performed the vacuum which took seconds, then upgraded, re-ran the refresh guide data, and ran the vacuum again.  Things seem to be resolved and working as intended.  If you're curious the reason I refreshed the guide data during that process is because when the server would become unresponsive I find that task stuck at 15% indefinitely and the DVR schedule would not display the normal artwork, also the DVR would just start recording random things from random channels.

I do wonder if I should change the other settings from the defaults, e.g. the db size of 96 mb and the row analysis of 400 lines and would welcome feedback on those items.

My Use Case: 500+ Blu-Ray movies which are fairly static now as I haven't bought any new media in awhile.  OTA in the southwest USA I pick up 123 channels and between that I am recording probably close to 18 hours per day. In the last 7 months I have added near 8tb of DVR content.

Server Specs: AMD 1700, AMD R9 290, 32gb ram, 2x8tb in raid 0 array, Debian OS with minimal package install, only running pihole and emby.

[Luke 42078]

Thanks for the feedback.

Quote

I do wonder if I should change the other settings from the defaults, e.g. the db size of 96 mb and the row analysis of 400 lines and would welcome feedback on those items.

Yes these can improve performance if you're willing to raise them higher.

[mwongjay 74]

@Luke Just curious - is the vacuum operation safe to perform on upgrades and downgrades? Is there a situation where you would not want to vacuum the db?

[Luke 42078]

2 hours ago, mwongjay said:

@Luke Just curious - is the vacuum operation safe to perform on upgrades and downgrades? Is there a situation where you would not want to vacuum the db?

I would think it would be fine, yes.