kraada wrote:kydechuk, Try the newly released beta - it has PostgreSQL tuning functionality which should improve performance across the board for you.
Kraada, tuning postgre feature is awesome, and it will be very useful for many users, but I had tuned my postgre to the top-speed already months ago. And it's not the solution for our topic's subject.
grobin wrote:What you can't do, is wait a long time for stats to show up while you're playing poker!
No things have more importance than this.
kraada wrote:We have been working hard to improve performance, but adding caching for the custom stats is not as simple as it sounds, there is a great deal of complex work that must be done behind the scenes since we will not go back to a system that requires manual housekeeping maintenance.
Nobody tells you this is very urgent thing to do, we are ready to wait. But we, as advanced users (I think I can call people who building custom stats and HUD's, having large imports and so on) and advanced beta-testers tell definetely to you that it's a problem and a lack of performance to not having cache for all of stats. If you keep it without changes, when the beta period will be over this problem will be obviously shows up to the surface.
