|
#1
|
|||
|
|||
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. |
#2
|
|||
|
|||
Re: PokerTracker Performance and SQL
Thanks,
I'm installing PostGresql this evening. Will upgrade my memory to 1 Gb ASAP |
#3
|
|||
|
|||
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. |
#4
|
|||
|
|||
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 |
|
|