PT3 is Slower than PT2 on my system

[mpethybridge]

Hi guys. I like the new look and features of PT3 a lot.

I am running PT3 on a HP Pavilion laptop with 1G of Ram and a 60G hard drive and the intel centrino duo processor. Windows XP. I have both PT2 and PT3 installed on this computer.

I am not sure if this is a bug, normal or operator head space and timing being off :D , but: I have both PT2 (postgresql) and PT3 set to open showing only my month-to-date stats (35,400 hands as of today). Total DB size is @400,000 hands. PT 2 loads my month-to-date stats in <1 minute, but it is taking PT3 4 minutes to display them.

I don't know much about computers and I know nothing at all about databases, so I don't even know what information I ought to be giving you other than what I have provided.

Matt

[APerfect10]

PokerTracker 3's queries are extremely customizeable therefore they are not currently very efficient. Some queries, especially filtered data may take longer. We expect to optimize these along the way.

Have you clustered your PT3 database? If you have not done that, you should. That could be one reason for slow data retrieval and will speed it up significantly.

Best regards,

Derek

[mpethybridge]

Yes, I have clustered after every import.

[Josh]

Do you have anything else going on during this time in PT3? Having multiple queries running at the same time (if you have other tabs loading reports) will cause each one to take longer.

[mpethybridge]

I didn't think I did, but when I fired up PT3 this morning with nothing else running, it took <1 minute to display my player list and stats.

This was probably the problem. I ran an import yesterday and then clustered; maybe it was still clustering when I first tried to switch to display my stats? I thought I waited for it to finish because that is what the dialogue box says to do.

Well, at any rate, no problem today.

Edit: Yes, multiple queries was definitely the problem; I recall that when it was taking a while to load I started tabbing from one page to another. Operator head space and timing was the problem after all! :lol:

Edit 2: I just removed my filter to display since the beginning of the month and the DB switched to display my lifetime stats in maybe 3 seconds. HOLY !@#$%^&*(!@#$%^& SMOKES, that is fast!!!! Very nice work guys!

[APerfect10]

There is a known issue with PT3 saying that the cluster has completed when in fact it has not. Give it a few more minutes after the completed message to finish. We are working to get this resolved.

Best regards,

Derek