Originally Posted by RedManPlus
As a software engineer...
I'm absolutely amazed that PT3 has forced...
1000s of marginally tech-literate people with countless computer environments...
To install and maintain a complex, database service...
When it will only be needed by people data-mining millions of hands.
Any light, stand-alone database with > max size than Access...
Or even a simple proprietary data structure...
Would have been fine for 99% of your customers.
I saw how PT2 worked with Access. When the database got to about 700M it would start to seize up and lag pretty badly. Now, with the current database schema, 700M is something like 70,000 hands in postgres. (I'm not sure if Access is more efficient at saving data; though I'd imagine not, starting at the same place is reasonable; I think my arguments hold if it's 60k or 80k hands just as well.) I've seen threads where players have played more than that in a week. Certainly anybody who plays full time will get there in 2-3 months if not much sooner. At which point there has to be complicated database rotation and it's a real mess. As I'm sure you're aware Postgres scales much, much better and really, once it's installed you can more or less leave it alone.
Originally Posted by InsideEdge
New beta dosnt work for me on ipoker either. I sent in a ticket.
Thank you for sending in the ticket; we'll be sure to look into your issue and get back to you.
Originally Posted by mocky
beta 13 wont work for me either on ipoker crashes at least once an hour very annoying sent in a ticket on Wednesday.
There were threads over at the PT forums relating to ipoker issues last week, heres one I happen to have bookmarked:
Thanks for your ticket as well, we will figure out what is going on and get these issues fixed and all of the data you have provided will be very useful.