Few questions regarding database housekeeping

[micstr]

Hi all.

When I bagun buying hands, my database started growing like crazy. I buy 1 milion hands every month. Now I'm doing a third batch, so alltogether I have about 3 500 000 hands and waiting for cache to rebuild. It's been rebuilding for 17 hours so far, but still about 10%, so alltogether it will be 18-19 hours. Is this normal?

I know, that after falling under 90% of cache, it will rebuild instead of updating, but is it not too long?

Maybe there is something that I'm doing wrong? How are you other useres dealing with your large databases?

Is it true, that PT4 will not need cache updating? That would be really great.

I'm running PT3 on fairly fast system: Win7, Intel core i5, 4GB of ram, HDD 7200, PostgreSQL 9.0

[kraada]

When it rebuilds it has to recalculate every stat for every player in the database - this is actually faster than calculating what needs to be updated, then doing the updating when the amount of updating is large enough, but we are aware it takes considerable time.

This is why in PT4 we've eliminated the necessity of dealing with this entirely - all cache work will be 100% behind the scenes in PT4.

[micstr]

So I understand 19 hours is a considerable time. OK, just wanted to make sure if there is nothing unusual in this matter :D

Really waiting for PT4 then.

Keep up the good work!

[kraada]

Yeah, my largest testing has been on a 14 million hand database which took about 25 hours to rebuild the cache on my machine.