Quote:
Originally Posted by 1meandog4u
When do you think I'll have problems with the size of my db? I'm using MYsql and I'm estimating I have over 400K hands. I did notice recently that it is "locking up" maybe once every couple of days.
I'm playing 6 tables, and have a few years of stats... About 1500 to 2000 hands a day, sometimes less when I have to mow the lawn, trim a tree... or other "honey-do's".
My database is so big, I can't install the most recent ver12 for 2010 because it would take me 12 hours (I know cuz I had to recently restore it in early January... sigh... THEN right after that you released a new snapshot and said, "You will have to rebuild your database..." Grrrrrrrrrrr
BTW, do we have to use the new config file with that new snapshot? If we do, more cut-n-pasting with table locations etc. work... work... work...
Dog
Hi Dog,
I meant to reply to this earlier, sorry for the gap ...
I dunno mate, I only have a fairly small db (say generally 20k-30k hands) and I only have 80k or 90k hands all time (if I even have the histories for all of them). If I make any rash comments about which db to prefer, you have to understand it's hunch and bias on my part as much as anything.
But I do suspect postgres is better at the serious size db's, so you might find a difference ... but having said that I think management is the key thing when you have that many hands. I think I would have several db's; a main db for playing (but only say 100k hands or less), and then maybe a series of 100k dbs for history. Then try out a small db occasionally when new code comes out.
Note that the new importer is definitely quicker than the old one - but then I dunno how much it will slow down on your size db ... but for 5-figure db sizes I think 50+ hands/second is possible/likely.
For the config file, I think you can just run with an old one generally, I've only just updated mine - you're right it's a pain
- sc