Remote Postgresql - hand import extremely slow

[muffinbubble]

Ok, just to update. On my work connection, a 2MB wired connection the problem is exactly the same.

I'll try our 8MB line some time today.

[muffinbubble]

I've just tried our 8MB line and no performance increase at all so I have no idea what the problem is. As I first thought, querying a database shouldn't take this long. It's taking 30 seconds or more just to even begin importing the first hand, and the log only has about 60 hands in total!

Locally it's instant.

[kraada]

I'm not sure either but I'll make sure to discuss this with our development team when I get a chance.

[muffinbubble]

Kraada, I put a link on StackOverflow - and it seems they are baffled too. I think it may be worth following:

http://stackoverflow.com/questions/4657605/remote-postgresql-extremely-slow

I starting to think the problem is related to PokerTracker some how - as queries I've been running myself remotely seem to run as expected.

[kraada]

I haven't had a chance to speak with a developer yet but as soon as I do I'll update you.

Could you also submit a PokerTracker.log file (it's created in C:\Program Files\PokerTracker 3\ whenever PT3 is started with Logging Enabled) showing the slowdown, then tell me the ticket number? That may also prove useful.

[muffinbubble]

Sure, submitted and ticket number is: 103392.

[kraada]

Thanks.

[xroot]

Hi,
The answer that the pokertracker was designed to work with local database puzzles me a little.
One would think that pokertracker and database communicate over TCP/IP and expect them to work over loopback and over network with at least similar performance.

I am interested in this because
I am experiencing a similar problem with poker tracker and a remote postgres database hosted on a linux VPS - it's _very_ slow.
The hands are importing at the speed of 1.6-2.0 hands per second to the remote database, while local import is almost instantaneous.
When I start a new table it takes a few minutes (since I finished playing the first hand @ that table) before the poker tracker menu icon appears on the table.
The network bandwidth measures at 2+ Mbps up/down on both ends and latency is 40 ms at most.
The linux VPS shows 99.9% CPU idle while import is going.
DNS and TCP/IP in general are both in check on both ends.
I moved the database because my laptop would start crawling when 20 tabling to the point of being unusable.

I wonder if you have time to perform the following test:
create a local listening port on your machine running pokertracker that's tunneled to the remote VPS' postgres listening port.
I.e. for pockertracker it will look like the postgres listening port is on localhost.

You can use a putty ssh client (free) and do something like this:
create a local listening port ( say localhost:5555), which is tunneled to your the vps host also running ssh and connecting this to postgres on port 5432.
You seem technical and there are numerous articles on the internet on how to do that (search: putty ssh tunneling).
Then change your pokertracker config to point to port 5555 on localhost instead of 5432.
In the end it will look like this:

pokertracker -- localhost:5555 -- ssh tunnel -- 5555:vps_host:5432 -- postgres

You can go further and replace the local listening port to 5432 so that pokertracker has no way of suspecting anything.
It will look local to pokertracker and i wonder if it makes the difference.

[kraada]

PT3 is extremely sensitive to latency. If you really only had 40ms ping times, things should be ok, but even a few hundred milliseconds would add up and quickly overwhelm PT3.

PT3 was designed to work with a local database because remote shared databases are uniformly outlawed by the poker sites. I understand the desire to have a VPS of your own to use so that your own data is more portable, but the latency can easily get beyond that which PT3 can handle easily causing slowdowns and other problems.

You are welcome to try using SSH tunneling - if you do I'd be interested to hear how well it works - unfortunately I do not have a VPS on which to test so I cannot run these sorts of tests myself.

[powerxaero]

Well I tested the SSH tunnel. Didn't make a difference for my problem (I just can import up to 1000 players, then all of a sudden the manual import freezes and I can't even stop the import process).