|
#1
|
|||
|
|||
Re: PokerTracker Performance and SQL
I totally sympathize with you. I have a Dell 8250. I've already upgraded to Postgres. My database size is about the same as yours. I have about 150 new files to import. When I run the damn program. it will more or less lock up the machine for more than 12 hours. I had to use the machine so I force rebooted.
The software wasn't built well if it constantly locks up the machine. I can understand if it's CPU intensive but better written software will run in the background and give you a visual progress report. I don't know what's it trying to do but the data size doesn't seem to warrant so much CPU usage. |
#2
|
|||
|
|||
Re: PokerTracker Performance and SQL
I had your problem once, but the way I solved it with
Pat's advice, is to make sure you import all your hands while you are actually playing rather than let them bunch up. And also make sure that after you import the hands, you move th history file to another folder. That way, Poker Tracker is only trying to import hands from the tables that you are currently playing at and it is much more manageable. I found this to be quite workable. But my other problems occur every time I try to access the tournament database. I was hoping to hear from others who have switched to PostGRESQL and how they like it. Suerte, Jonathan |
#3
|
|||
|
|||
Re: PokerTracker Performance and SQL
For me, moving to PostgreSQL made a noticable difference but not a dramatic one.
Going from from 512MB to 1GB of RAM had a bigger effect. |
#4
|
|||
|
|||
Re: PokerTracker Performance and SQL
Thanks,
I'm installing PostGresql this evening. Will upgrade my memory to 1 Gb ASAP |
#5
|
|||
|
|||
Re: PokerTracker Performance and SQL
I'm running the PostgreSQL database off of my linux machine and I can tell you that as I acquire more hands it takes longer and longer to open. Response time suffers when switching tabs as well. One of these days I think I might convert back* to access to see if PostgreSQL really is better.
*NOTE: Converting back to an Access DB requires exporting all hands and then re-importing them. I posted about these response issues on the PT board but wasn't met with many answers. I suppose running the DB remotely (on my linux fileserver) could explain the slow response, but I'm not sure. |
#6
|
|||
|
|||
Re: PokerTracker Performance and SQL
Interesting....
Last night I started the conversion process. I have 5 databases, and last night I converted the first, and smallest..MyFirstPokertrackerDatabase. Even though this particular databse is small, it took about 2 and half hours to convert. I'm going to go through one a night until its complete. Mabey, I'll try getting a new machine and see if that helps. Jonathan |
|
|