Rebuilding cache working too slowly

[mvladimir]

I have a DB with 2M hands.

Every day I want to import about 300K hands but I have a problem - rebuilding cache working too slowly, it working with my DB about 20 hours(too long). I must to rebuild cache every time when I import new hands or is this not necessary? Will be some problems if not to do rebuild cache every time?

Thanks.

[kraada]

In PT3 keeping the cache up to date really is a necessity for keeping things working smoothly. There is no way to speed things up in PT3, but there is a good solution for you: upgrade to PT4! PT4 keeps the cache up to date at import time so you never need to rebuild or update the cache manually. So once import is done, you're ready to go.

[mvladimir]

In PT3 keeping the cache up to date really is a necessity for keeping things working smoothly. There is no way to speed things up in PT3, but there is a good solution for you: upgrade to PT4! PT4 keeps the cache up to date at import time so you never need to rebuild or update the cache manually. So once import is done, you're ready to go.

I already have PT4 installed but I have the problem like in this thread https://www.pokertracker.com/forums/viewtopic.php?f=58&t=43378(I sent my logs and bug reports about this problem). I can't to use PT4.
So... after manual import I must update cache? But my update cache working too slowly maybe exists some settings to speed up this process, maybe some settings for postgreSQL? I need some solution. How I already wrote my rebuild cache proccess working about 20 hours with my DB(2M hands), I import about 250K-300K. What can I do? If I not update the cache after each manual import what will be?

Thanks.

[kraada]

What might work best for you would be to import smaller chunks of hands and update the cache after each one. As long as you import less than 10% of the current database size in hands Update will run rather than Rebuild and that might end up working out to be faster for you. It'll be a bit more tedious this way but it'll work.

Running without a full cache slows down data retrieval at the table by a very large amount and is not recommended.