#1
|
|||
|
|||
does PT slowdown other people\'s cpu\'s?
it seems to kick mine in the groin. i have compacted, but my database is pretty big (~800 MB). do i need to make a new database or something?
thansk. |
#2
|
|||
|
|||
Re: does PT slowdown other people\'s cpu\'s?
I assume you're using ACCESS and haven't converted to Postgres SQL?
Do yourself a favor, at least get up to Postgres. Or ever better, get a second PC, something in the $600 range, setup a small network, and run Postgres on the second PC. Puts 99% of the load on another CPU. I have 500k+ hands in my DB and 8 table without issues this way. |
#3
|
|||
|
|||
Re: does PT slowdown other people\'s cpu\'s?
Do you have PT loaded on just one of the computers? If so I guess you just map any shorcut for PT to that drive?
Thanks |
#4
|
|||
|
|||
Re: does PT slowdown other people\'s cpu\'s?
thanks, i'll try that.
|
#5
|
|||
|
|||
Re: does PT slowdown other people\'s cpu\'s?
PT is not multitasking friendly, it claims almost exclusive access to your CPU when its processing, which is why you experience slowdowns.
Using a 2nd PC to run PT, thereby dedicating a CPU to it is the best route. You could also reduce the time between updates, so that its not slowing you down all the time, and uncheck autorate on import, if you don't have a 2nd computer. |
#6
|
|||
|
|||
Re: does PT slowdown other people\'s cpu\'s?
That has to be annoying looking up your table on a different computer every time you hop to a different table.
|
#7
|
|||
|
|||
Re: does PT slowdown other people\'s cpu\'s?
Obviously the computers should be networked and the HUDs should have no problem finding what they need.
|
|
|