Optimizing PT performance for BIG databases...remote database?

[jukofyork]

[ QUOTE ]
Do you use a HUD at all? I saw that PM had one included, but people seemed to be complaining about how well it worked. With a HUD, it seems like it'd be quite a good product.

[/ QUOTE ]
Yep, I did use the PM HUD but agree it needs some work (and is Party only atm), but I'm not really one for using vast amounts of stats whichever HUD I use (VPIP/PFR/AGR/WtSD/#Hands).

I'm pretty sure if more people tried PM and took an interest, then it could develop into a much better product than either PT (or PO) for dealing with large amounts of data.

Juk [img]/images/graemlins/smile.gif[/img]

[_dave_]

Hi all,

just found this interesting tit-bit on the PT Postgres forum:
http://www.pokertracker.com/forum/viewtopic.php?t=15282

Good news: Looks like PT import may get near a 50% boost in speed if this is accurate - I just made some small import logs myself and it looks accurate, but I didn't really do a great deal of study on the matter. It was only posted today, but it seems like a fairly simple change for PT Pat to make [img]/images/graemlins/smile.gif[/img]

Bad news: I'm gonna have to go in to work tomorrow and scour the database functions we use and purge all occurences of SELECT MAX(..., fun times [img]/images/graemlins/smile.gif[/img]


Network setup - FWIW I think ideal setup would be three computers on the gigabit LAN

Computer 1 - Playing machine, decent spec - (Your current playing machine sounds overly capable). PT installed but only for session review etc. No PT imports runnning on this machine, HH folder shared on network. use VMs to mine hands with space capacity.

Computer 2 - Postgres server, Linux? decent CPU, fast disk (iRAM?), plenty fast RAM. Prolly can run a VM or 2 on this also.

Computer 3 - PT import machine, Very fast single core CPU (Maximum GHz, PT won't use a second core - overclock the P4 maybe?), and pull played/mined hands from network share, import to DB on Computer 2.

Would likely be a nice setup [img]/images/graemlins/smile.gif[/img]

dave.

[Entity]

[ QUOTE ]
Hi all,

just found this interesting tit-bit on the PT Postgres forum:
http://www.pokertracker.com/forum/viewtopic.php?t=15282

Good news: Looks like PT import may get near a 50% boost in speed if this is accurate - I just made some small import logs myself and it looks accurate, but I didn't really do a great deal of study on the matter. It was only posted today, but it seems like a fairly simple change for PT Pat to make [img]/images/graemlins/smile.gif[/img]

Bad news: I'm gonna have to go in to work tomorrow and scour the database functions we use and purge all occurences of SELECT MAX(..., fun times [img]/images/graemlins/smile.gif[/img]


Network setup - FWIW I think ideal setup would be three computers on the gigabit LAN

Computer 1 - Playing machine, decent spec - (Your current playing machine sounds overly capable). PT installed but only for session review etc. No PT imports runnning on this machine, HH folder shared on network. use VMs to mine hands with space capacity.

Computer 2 - Postgres server, Linux? decent CPU, fast disk (iRAM?), plenty fast RAM. Prolly can run a VM or 2 on this also.

Computer 3 - PT import machine, Very fast single core CPU (Maximum GHz, PT won't use a second core - overclock the P4 maybe?), and pull played/mined hands from network share, import to DB on Computer 2.

Would likely be a nice setup [img]/images/graemlins/smile.gif[/img]

dave.

[/ QUOTE ]

3 comps is overkill, unfortunately, for my office. I'll probably just have the Import comp be the same as the SQL server unless there really seem like there will be issues with doing that. Having the SCSI 15kRPM HD should really help speed things up I think.

Rob

[_dave_]

[ QUOTE ]

3 comps is overkill, unfortunately, for my office. I'll probably just have the Import comp be the same as the SQL server unless there really seem like there will be issues with doing that. Having the SCSI 15kRPM HD should really help speed things up I think.

Rob

[/ QUOTE ]

3 comps is indeed a bit of overkill - so long as the play computer is not doing the import I expect it will be smooth runnings [img]/images/graemlins/smile.gif[/img]

dave.