Clustering Problem

[meatbird]

Hi, I have bought a register version of PT3.

My database is a bit larger nearly 40M hands in the database, and it becomes very slow weeks ago,
I tried to do clustering twice in past 10 days, it takes nearly 20 hours every time,and at last there is
always an error msg "Can not drop holdem_hand_player_details table!". I am sure there is no application
will use "PT3 DB" when I did cluster.

Do you have any suggestions or ideas of my problems?

And here some other questions:
1.IF I can not do the cluster, will it be helpful/same if I delete the database and re-import all the hands again?
2.If I use a server to run the database and the server only import hand-history files and do not have any other
application access the harddisk/partion, Will it be helpful to speed up the database as its scale growth?
3.Do you have any suggestion to deployment for a database with huge number of hands?


Thanks!

[WhiteRider]

What version of PT3 are you running?
When you did the "clustering", did you do all the Housekeeping options including the cache?

Have you read the performance tweaking threads?
Performance Tuning: Hard Drives
Performance Tuning PostgreSQL

I haven't had experience with such large databases myself, but the general recommendation is to have datamined hands (I assume a significant part of your database is mined!?) in separate DBs which you start fresh each month (or whatever) and just use the last 2 or 3 in the HUD, rather than having one huge DB with everything in it. This will also mean that once you have a previous month's DB cached it won't need doing again and will remain fast.

2. Yes, if you have just postgres running on a system it will be faster.

[meatbird]

Thank you for your quick reply.

What version of PT3 are you running?
A: v3.00 beta 17

When you did the "clustering", did you do all the Housekeeping options including the cache?
A: I run the housekeeping with "Clustering", "Vacuum","Analyze". It didn't include cache.

Have you read the performance tweaking threads?
Performance Tuning: Hard Drives
Performance Tuning PostgreSQL
A: OK, I will try to tweak the options you recommended.


I haven't had experience with such large databases myself, but the general recommendation is to have datamined hands (I assume a significant part of your database is mined!?) in separate DBs which you start fresh each month (or whatever) and just use the last 2 or 3 in the HUD, rather than having one huge DB with everything in it. This will also mean that once you have a previous month's DB cached it won't need doing again and will remain fast.

2. Yes, if you have just postgres running on a system it will be faster.[/quote]

[WhiteRider]

You should include the "cache" option when you do Housekeeping, this will give you the biggest speed benefit.