Should running a full house-keeping require free HD space?

[domino66]

I tick all 4 boxes for a complete housekeeping sweep on my PT3 DB, but I get an error msg about half way through implying that I'm out of disk space. FWIW, my HD is 106 gigs , and I'm being told that 17gigs of that is still free. I don't really get this...does running housekeeping require HD space, and if it does, i would have thought that 17-gigs would be enough!

[prajna]

No. You should have plenty of space left for this. Enable logging (Submitting a pt3 log file) try to do housekeeping again, then attach your pokertracker.log file (path below) to a support ticket so we can see what is causing this:

C:\Program Files\Pokertracker 3\pokertracker.log

[WhiteRider]

As I understand it, the housekeeping functions (particularly Clustering) needs about the same amount of free disk space that your database occupies.
Do you just have one Postgres database on your computer?
If so, have a look at how much space the whole 'data' folder under postgres takes up. Is that more than 17GB?

[domino66]

Um, you guys are saying drastically different things.

Yes, I have more than 1 postgres DB on my computer. What I can tell you is that when I restored the DB on this machine (a laptop), it went from having about 49 gigs of free space down to 17 (so I'm guessing that means it occupies about 32 gigs of space >> it has about 8M hands in it...does that seem about right??))

Anyway, I simply don't have the ability to clear another 15 gigs, any options for me here?? If I can't run a full housekeeping, I can't get TT to search in a timely fashion. Why does the clustering process NEED that space anyway (b/c it doesn't actually fill that space up after the cluster...the same amount of HD space is free both before and after the cluster!?)

[kraada]

Not having enough free space shouldn't stop the cluster entirely, it will just slow it down significantly.

The cluster process that PT3 uses completely rebuilds the database from scratch, as such it needs a significant amount of temporary space. Once the database is completely rebuilt, it deletes the old database and uses the new rebuilt one. About 32G of memory for an 8M hand database sounds about right.

You might want to consider breaking your one database up into smaller segments. I personally keep databases for observed hands month by month. That way, once the month is over, I never need to reperform housekeeping on those hands (and, after 4 or 5 months I can just delete the obsolete data if I'd like).

Also, you can try just running the Caching process which shouldn't use that much free space but should significantly improve the TT speed.