big database, lots of stats, poor performance, PT-Omaha
Posted: Tue Sep 30, 2008 8:52 pm
so i was just reading the links in another thread about a big database and i have a few questions (didn't want to hijack that thread).
so i play omaha, generally 4-6 tables, with PT omaha and Poker Ace, on full tilt. I have 2 databases, both postgres 8.3. the first one probably has a million hands, the second one half a million. there are probably 100k hands that are mine, the rest are datamined.
when i have 4-6 tables going i often get the yellow screen of death, especially when i leave a table or join a new table and the lobby comes up. it results in me being sat out on all my tables/hands.
so here are my questions: should i ditch postgres 8.3 and go postgres 8.2 so that i can create a cache? if so, can i do this without losing my current databases? also, does having up and refreshing a lot of stats (i have like 20 stats) every 5 hands slow me down?
any input on how i can improve performance would be much appreciated.
so i play omaha, generally 4-6 tables, with PT omaha and Poker Ace, on full tilt. I have 2 databases, both postgres 8.3. the first one probably has a million hands, the second one half a million. there are probably 100k hands that are mine, the rest are datamined.
when i have 4-6 tables going i often get the yellow screen of death, especially when i leave a table or join a new table and the lobby comes up. it results in me being sat out on all my tables/hands.
so here are my questions: should i ditch postgres 8.3 and go postgres 8.2 so that i can create a cache? if so, can i do this without losing my current databases? also, does having up and refreshing a lot of stats (i have like 20 stats) every 5 hands slow me down?
any input on how i can improve performance would be much appreciated.