FAQ: Rush Hud Performance Tuning

[nelliesman93]

Is it best to use the PostgreSQL Tuning Wizard for advanced optimization or to use the recommended settings listed by Tarix?

[tarix]

Is it best to use the PostgreSQL Tuning Wizard for advanced optimization or to use the recommended settings listed by Tarix?

They should be really close. Is the EnterpriseDB Tuning Wizard highly disagreeing with me?

[nelliesman93]

These are my settings after running the Tuning Wizard.

2GB machines:

Code: Select all
work_mem = 1024
shared_buffers = 1024
logging_collector = on

[tarix]

Which of the three options did you pick to get those settings?

[MathP]

Was there any solution for the Hud showing stats for past hands when you quick fold a few in a row? (I think it was TechVoodoo having that problem...)

[nelliesman93]

Which of the three options did you pick to get those settings?

I followed the procedure in the following link and selected mixed.

PostgreSQL tuning:

viewtopic.php?f=45&t=10393&start=0&hilit=%26quot;tuning+wizard%26quot;

[tarix]

I followed the procedure in the following link and selected mixed.

If the Tuning Wizard settings are working well for you then go ahead and use those. If the performance feels worse try a bit more conservative settings. There's definitely a balance to be struck between the shared_buffers and the operating system cache but it sounds like my settings might be too low.

[nelliesman93]

What exactly should I be looking for with the tuning? Is there a good thread that discusses the intricacies of tuning or shows exactly what performance gains/losses we should expect by adjusting them?

My HUD comes up fairly quick. I really don't know how to gauge it. We need a HUD performance emulator.

[tarix]

What exactly should I be looking for with the tuning? Is there a good thread that discusses the intricacies of tuning or shows exactly what performance gains/losses we should expect by adjusting them?

My HUD comes up fairly quick. I really don't know how to gauge it. We need a HUD performance emulator.

There are many articles on the internet that discuss tuning postgres. Much of the information doesn't apply to PT3 since they are discussing tuning large database servers dedicated to data processing. Reading some of those articles might help or it might just add the confusion.

If you enable logging we do write query performance data to the log file. In particular you want to search for "POP0" and "EVY0" as those are the two hud queries that are likely to take the most time. Any settings that lower the average query time are definitely an improvement. Generally once you have them around 300ms or less your postgres is fast enough.

[nelliesman93]

In particular you want to search for "POP0" and "EVY0"

I searched for both in the log and only found "POP0" My times were not very consistent. Here are a few:

1146
617
925
728
590
806
639
592
609
561
1153