The biggest bottleneck is actually hard drive seek time; if your computers are reasonably similar and the only difference is RAM, having the postgres installation on a separate computer will actually make things quite a bit faster. If the postgres computer is more than a few years old it might change things but I haven't done any specific testing on this to be able to give you a more concrete guideline than that.
what do u mean exactly "if your computers are reasonably similar and the only difference is RAM, having the postgres installation on a separate computer will actually make things quite a bit faster". ALso from client computer how can i display the stats as i dotn want to be importing into one databse from two pt3's. DO i? IS it ok to do that?
The thing that slows PostgreSQL down the most is the hard drive. When you run PostgreSQL on a separate computer it has its own hard drive not doing anything else but database work. This is much faster than using your computer to play (which uses your hard drive) as well as import.
You won't have any problems using two machines like this unless you're planning on importing to the database at the SAME TIME on both machines. If you're going to do that, create separate databases for each computer. You can still use both databases for the HUD though; reading from multiple databases like that won't cause a problem.
zedjr wrote:U didnt really answer any of my questions. how can i from client computer run pt3 hud if i am not importing.
You can't run the HUD if you are not auto importing. If you want to use the HUD on one computer connected to a shared database then you should not be importing into that database from any other computer at the same time. You can use any PT3 connected to that database, but only [import from] one at once.