Why does TT give me this error every time I run it?

[domino66]

I press "Start Search", and nearly immediately it gives me an error that says "There were no tables that met your criteria". I press OK, and it immediately generates another error window that says the same thing. I click OK to close it, and then strangely the 'search' still seems to be running because slowly (and i do mean sloooooooowly, like one table every 30 seconds or so) tables start showing up in the upper "results" window. Why does it give me those two error messages and then seem to continue the search?

And it's still brutally slow to the point of being more or less unusable to this point...
are these known issues with TT?

[WhiteRider]

Make sure you are running Beta 18.
Download and install PT3.
Beta 18 release notes.

If you are selecting no limit tables you must check the big blind amount not the 100x buy-in amount that some sites quote.

[domino66]

That answer didn't really make sense; allow me to explain:

I am definitely running PT3 Beta 18.
I am aslo definitely ticking the checkbox with the big-blind amount.

Here, let me give you the specifics:
My DB has about 7-Mil hands in it; it's been freshly clustered/vac'd/analyzed.

I tick "PartyGaming" as the only site. I put tickmarks next to "$200NL", "$100NL", "$50NL", "$20NL", "$10NL".

I press Start Search. Immediately it gives me the error box I described, and then pops up the same error box again (I have to close it twice).

But here's the really perplexing part: after i close that error box twice, it continues the search and starts populating the results windows with tables albeit VERY slowly like i said: the search has been running 6 mins now and it's only found 7 tables (and it's still searching).

[WhiteRider]

Yes, OK, I get that message box about no tables matching the criteria, once for each level that has no tables - I guess no-one is playing NL for $100/$200 blinds at the moment.. ;)

I've just done the same search and it's found 30 tables (all $10 and $20 NL blinds) with between 5 and 10 players at the tables.

I guess the slow updates must be to do with the size of your database.
How fast is your system? Do you have a good fast hard disk with plenty of space?
Is there much else running?

You might also want to check out these 2 posts:
Performance Tuning: Hard Drives
Performance Tuning PostgreSQL

[domino66]

Yes, OK, I get that message box about no tables matching the criteria, once for each level that has no tables - I guess no-one is playing NL for $100/$200 blinds at the moment.. ;)

OK, well obviously that's a bug that you'll fix in the next release right? I don't need an error box to let me know that.

I guess the slow updates must be to do with the size of your database.

My DB is only about 6M hands...yes, sizeable, but definitely not outside of the realm of reasonableness. I have about 1M hands at each of 6 or 7 sites. Yes, I have a fast computer with 2 gigs of RAM and plenty of free HD space (well, about 60 gigs out of 240 remain free).

Like I said, it was populating the results window with about 1 new table every 45 seconds...so it would have taken nearly 20 minutes to dispaly all 30 of the tables you say were available...and that's only on one site! Clearly it's unusable in this state...I thought part of the purpose of building the cache was so that queries like this were lightning fast >> go re-read my post from a month ago about all the ways that you need to look at improving TableTracker. I took me quite a while to write that post but few, if any, of those suggestions (many of which culled from Sixth Sense, which really did get it right in many respects) have actually been implemented.

Does the cache functionality not extend to TableTracker (i.e. ONLY the HUD)? If not, any reason you can't also make use of a cache-type feature to make TT run fast enough to be useful...?

Thanks for your continued attention to this!

[domino66]

Ugh, this is so annoying -- so I followed the instructions in the posts you linked to above about improving performance.

I changed the values in the postgres.config file (and immediately noticed a modest improvement). Then, as your instructions dictated, I stopped the postgres service then defrag'd my HD.

Now, TableTracker actually finds tables pretty quickly (maybe 1 table every 10 seconds instead of every 45), EXCEPT it generates an error that says "There were no players found that had stats in the database", and in the lower window in the TT tab, it says "Unable to load query into report. Reason: Attempting to access a null pointer (class ResultSet"

Any idea what this error is all about? It seems to be finding the tables alright and populating the upper TT window, but is not displaying any of the players seated at the tables in the lower window...only the error message i mentioned above. Could the defragging have anything to do with this? TT worked fine (but slow) after i changed the postgres.conf file...but it was after the defrag that it started giving me the errors above.

Ugh

[domino66]

By the way, now I can't even connect to the postgres server. I have no clue how any of the settings i changed or the defrag i performed could have caused this -- when i open pgadmin III and double-click the entry that is on port 5432, i get the following:

[ img ][ img ]

[WhiteRider]

This means that postgres isn't running.
Please try starting the postgres service: Start -> Programs -> PostgreSQL -> Start Service.

[domino66]

This means that postgres isn't running.
Please try starting the postgres service: Start -> Programs -> PostgreSQL -> Start Service.

For some reason that's not doing the trick. It's not properly starting the PostrgreSQL 8.0 service (even tho, yes I went to Stars/Programs/8.0/Start Service. Even tried a reboot, and then starting the service. No dice.

See my post above, is there anything that I did to that config file that could have caused this because that's the only thing I changed (in addition to defraging my HD).

EDIT: Obviously it won't surprise you that NONE of my programs that rely on 8.0 (that's PAHUD and PT2 for the most part) are working anymore. I have no clue what's going on >> why can't i connect to the postgres server??

[WhiteRider]

I think those settings were for 8.3, so I'm not sure if they are the same for 8.0. Is there a reason you are still using 8.0?
Have you searched for the postmaster.pid file?
I'll get someone who knows more about postgres to take a look at this thread.