Table Tracker very very very slow?

[ddrewno]

Today just trying to do a search for FTP 100NL table it took over 7 minutes. It has been getting progressively slower and slower as time goes on. Is this because my database is ever-increasing in size? I've probably data mined about 500,000 hands since creating this database. I just clustered the database (No clue what that even means, although I assume it's like compacting) yesterday, and the problem is still getting worse. I'm using PT3 V3.00 Build 2 right now.

I'm running this on Vista on a machine I built myself that is extremely fast, and I still have and regularly use PT2. My PT2 runs without any flaws and very quickly, and it definitely points to its own SQL database and has had no problems.

To be clear: This was working perfectly fine for about 3 months, and it has been getting progressively slower and slower as time as gone on, and lately it is starting to get unbearable. I have no other problems with this program at this time.

[Peligroso]

Hello, check out our Performance Tuning PostgreSQL Guide and see if that helps at all with this. In the next Beta, I believe these TableTracker queries should be faster since it will be using the new cache which will be introduced.

[ddrewno]

Thanks for the link. I followed the steps and now my searches are returning in about 1 minute which is 100% acceptable to me. The exact lines I added were:

shared_buffers = 65536 # min 16, at least max_connections*2, 8KB each
work_mem = 32678 # min 64, size in KB
maintenance_work_mem = 131072 # min 1024, size in KB

I have 2gb of ram, and it's working great now.

[Peligroso]

Good to hear :)