SQlite size questions

[martint123]

7 days, 75-ish channels and doesn't seem to vary much from 10mb. 'empty and reload' each night.

[carpeVideo]

I found mine to be 100GB once - I re-installed wish I had seen vacuum.

It hasn't repeated yet.

[Flash_]

Top tip, thanks. 39MB down to 1MB. EWA was getting slow to respond even on a very fast pc.

[tiger66]

I recently reinstalled GBPVR (1.3.7) after reloading Windows XP on my PC and got everything set back up again and working (analog and digital). I noticed some slowdowns in performance and checked and my gbpvr.db3 is over 12G!

Running the vacuum now...

[sub]

It wont have been related to 1.3.7. As seen by this thread, some bug in SQLite can occassionally trigger the SQLite database to go nuts and grow to stupid sizes. Luckily the problem is very rare, and we see very few reports of it happening. All you can do about it is vacuum the database, or delete your database and set it up again from scratch.

[tiger66]

:o No, sorry, was not implying it had anything to do with the latest release. I had been running 1.3.7 before I decided to re-install Windows XP and had no problems with the database. GBPVR has been working great for me... Windows XP on the other hand had gotten extremely slow. I think my latest problems with the slowdowns after the re-install are related to not having everything, especially the decoders, back up to snuff yet.

BTW, after running the "vacuum", the size of the database decreased from 12G to 9.5M. Huge difference!

Thanks sub for the tip.

tiger

[dennit]

7 days, 75-ish channels and doesn't seem to vary much from 10mb. 'empty and reload' each night.

I have 500 channels (650 source channels) and 11 days in a 45MB db. About 400 of the channels have guide data. The rest are PPV/VOD or network affiliates from outside my area where I don't have data or it's a duplicate of my local affiliate and I don't need it. The principal effects I see from this large size are:

1) On startup, it takes a while (2.5 minutes) to load the guide. I usually watch a previous recording or video, instead of the guide to give it a chance to load. This isn't really a problem.

2) It really dislikes canceling a recording while it is recording - particularly a long recording like a sports game of 3+ hours. It has no problem canceling prior to starting the recording - that's instantaneous, as is scheduling and updating recording parameters. It often completely refuses to cancel during a long recording. If I really need to kill it so I can tune to another channel, I exit, stop the recording service, manually edit the gbpvr.db3 database to remove that entry from the recording schedule table, then restart the service and then restart pvrx2.exe.

I've been thinking about writing a quick batch file to do this for me, but I don't need to do it very often.

[sub]

Or you could get rid of some of the channels that you never watch, or reduce the number of days of listings you're pulling in.

You probably only uses 50 or less of those channel.