rush poker hud overlay

[gone an flone]

hi,
i was able to inmport full tilt hands and to configure the hud.
im using windows 7, run FT and PT 3.06.2 as administrator (trial version of PT if it matters). postgresql 8.4.
here is an image of how the hud pop up:
[ img ]

Uploaded with ImageShack.us

at this moment im not able to make any action at the table until i stop the hud at the import window.

[WhiteRider]

You have changed one of the popup groups to be 'show on table for everyone'. You can change it back to 'popup use only' - see the Tutorial: Managing HUD Groups.

If you're playing Rush tables you may want to update to beta v3.07.1 as there are further improvements for Rush in that version.
Download page
PT3 Build History / Release Notes

We've found a setting in PostgreSQL 8.4 which should speed up the slow queries we see in some cases with 8.4.
Please try this:

Edit the postgresql.conf file (Start > Programs > PostgreSQL 8.4 > Configuration Files > postgresql.conf) - if you're using Vista or Win 7 then right click > Run As Administrator in order to be able to save the file.

On Mac the files are in /Library/PostgreSQL/8.4/data (note: not ~/library) and you can edit them with any text editor. If you don't have permission see this page.
Mac Files and Folders

Find "from_collapse_limit" and "join_collapse_limit" and set them both to 12. You must REMOVE the # from the start of the lines, like this:
from_collapse_limit = 12
join_collapse_limit = 12

Save the file and then Start > Programs > PostgreSQL > Reload Configuration (on Mac: Applications > PostgreSQL 8.4 > Restart Server).

That should help performance.

[rowhousepd]

Is there a reason why 12 is the magic number here? I mean, if I'm still not seeing a lot of difference (which I'm not) would making it higher or lower make things run differently? Not sure what a collapse limit does exactly.

[WhiteRider]

I believe it was mostly through experimentation (by the development team) to find the value which gave the fastest queries.
From v3.07.2 onwards you shouldn't need to make this change manually.

[tarix]

Is there a reason why 12 is the magic number here?

It has to be greater or equal to geqo_threshold. The improvement is on the order of 300% so if you aren't seeing an improvement then you likely didn't have the problem in the first place. Have you submitted logs of the slow queries?