Closing

[Nekitor]

-Windows XP
-error both with pokerstars and partypoker
-PT3

During the scan after 1-20 minutes of working the program just closes. If not scanning it is not closing
Tried to reinstall several times and installed new net.framework
Help please

[Zandry]

Can you add me to AIM/MSN/ICQ/Skype, and I will help you figure out the problem

AIM: ZandryTST
MSN: zandry@tablescanturbo.com
ICQ: 571846001
Skype: ZandryTST

[Zandry]

Here's some other ideas I posted for someone else with the same issue. Please do try to contact me on AIM/MSN/ICQ/Skype if you can, I would very much like to figure out what is causing this all the sudden. The fact that it's happening on both pokerstars and partypoker implies to me that it is a database problem for a few people, possibly caused by me upgrading npgsql to a newer version

- What version is your postgresql?
- Try downloading and running this fix.bat (with tablescan and stars closed): http://www.tablescanturbo.com/files/ftpfix.zip
- Could you go in Database > Manage databases and uncheck all your databases, so you have no active database. Then leave it running for an hour or two and see if it crashes. That would help me determine if it is a database issue
- If it works with no database, you might want to try changing the "host" of your database from "localhost" to "127.0.0.1"
- Could you turn on "verbose logging" at help > logging. Then each time after it crashes, go to C:\Program Files\TableScan Turbo\logs and make a copy of lastscan-verbose.log and email it to me. Make sure you get the log file before you scan again, as it will get overwritten on every scan so it doesn't get too large

[Zandry]

Ok, I believe I have figured this issue out, it was caused by my commandtimeout variable being set too low, that's why it's just happening to a few people, all PT3 users or Elephant users. Somehow it would cause TST to crash when the database query timed out, my best guess was the older version of npgsql was ignoring the commandtimeout variable and that's why I never saw it until I upgraded

First, try this update:
http://www.tablescanturbo.com/files/TableScanTurbo_Update-RC4-b6-3.exe

And tell me if it works. Once you've determined that it works, I want to suggest there is a very simple way in TableScan to make your database results way faster so you never would have experienced this problem, go in TableScan to Database > Manage Database and Edit your database. There should be an option "Scan results from player cache only", make sure that this is checked. This will make your database results way faster. But, if you're willing to test the above version for a few hours before you change that setting, it would be very helpful to me to know if the problem is fixed or not

[Nekitor]

I changed localhost and updated scanner, and i already work for 2 hours with no crashes, so ty for help.

tables:9
players:89
time:331s
(party)

i think before update it was faster but no so fast as i wanted

is this time ok? sometimes 600s.

Is this a problem of my hardware? Can a better computer improve speed?

[Zandry]

I changed localhost and updated scanner, and i already work for 2 hours with no crashes, so ty for help.

tables:9
players:89
time:331s
(party)

i think before update it was faster but no so fast as i wanted

is this time ok? sometimes 600s.

Is this a problem of my hardware? Can a better computer improve speed?

9 Tables on partypoker should take 5 seconds or less than for tablescan to actually scan out of the lobby. For example, if you go in Database > Manage databases and uncheck all your databases so you have no active database, then scan and see how long it takes.

So it sounds like its just taking forever for it to get your database results. If you're using PT3 it would definitely help to go in Database > Manage Databases > Edit Database and turn on the "Scan results from player cache" option, this will make it way faster. You might also want to experiment with the option "Give TableScan threads highest priority" in configure > advanced settings > performance, try turning it on or off and see if it has any effect.

I wouldn't imagine it could take 330 seconds to do 80 players even on a really slow computer with a huge database, so I don't know I'm very confused that is a very long time :( As I said it should take about 5 seconds at most to scan 10 tables on partypoker

[Nekitor]

"Scan results from player cache" option - the scan is fast but i do not have enough information
Give TableScan threads highest priority" is on
Without active database? the scan takes 10 seconds. I really have huge database with ~1 million hands or more so i guess this is the reason.

I thing i should delete unuseful hands somehow, but i dont know how.
Could be another decision?

[Zandry]

"Scan results from player cache" option - the scan is fast but i do not have enough information
Give TableScan threads highest priority" is on
Without active database? the scan takes 10 seconds. I really have huge database with ~1 million hands or more so i guess this is the reason.

I thing i should delete unuseful hands somehow, but i dont know how.
Could be another decision?

If you just go in PT3 and update your cache, then it will go way faster, and you will have all the stats. Its in the "Database Housekeeping" window I think. 1 million hands is not that huge but if you have a slower computer and youre not reading from the cache then that would be pretty slow i guess.

[Nekitor]

Hi again. It scans 1000 players and 100 tables for 50-100 seconds.

I use HM2 and did database optimization full

Is it ok or can be faster?

[Zandry]

Hi again. It scans 1000 players and 100 tables for 50-100 seconds.

I use HM2 and did database optimization full

Is it ok or can be faster?

100 tables in 50 seconds is pretty good, in 100 seconds it's not that good, the question is, is there any database lag, the way you can tell this is in TableScan, when you scan, does the # of tables and players keep up in the "Status" panel, like does it say 50/50 tables or does it say 25/50 tables and then catch up at the end?

[Nekitor]

it is like this 19/20, 20/20, 20/21, 21/21 and to the end.
I scanned with no active database but it is still 140 seconds for 1500 players
I think reinstalling TST can help but i do not want to lose all settings and notes

[Zandry]

Well yes clearly it's not an issue with your database. Do you have configure > selection speed at fastest? When you watch the lobby, does it look like the playerlist is loading faster than TST is reading it?

Reinstalling TST should not do anything, but you can of course easily save all of your settings by making a copy of C:\Program Files\TableScan Turbo\config. Maybe a better idea would just be to install TST to a different folder, then you could see if a fresh install was any faster

[Nekitor]

That problem was connected with my wifi connection but a have a new one :)

It happened after one of imports (I was Importing 300-500k hands to my HM2 everyday for 2 weeks)
TST is reading the playerlist very slowly, but before that import it was ok.
It is like this 1/10, 2/20 and to the end.
I tried to scan my old HM1 database and the scan was fast.
Did full base base optimization. (did not do postgresql tuning can it be helpful?)
I guess there is some critical database size so i should delete some hands?
(Database size: 8548 MB)
I think deleting some hands can help but i dont want to do it, maybe i can solve this problem in another way?

[Zandry]

Well, right now my suggestion would be Configure > Settings > Performance, play with those 2 settings, try turning on restrict tablescan to one database thread, and turn on highest priority, and see if either of those help.

Anyways it's really interesting, I had never heard this problem before with HM1, but now a few people are having this problem with HM2, I'm gonna need to look more into this and see if there's anything I'm doing on my end that is somehow causing this problem. The query for HM1 and HM2 are almost exactly the same, except the HM2 query I have to add one more "where" statement to make sure that the hands are not tournament hands. So, it's quite interesting, I don't know why it's happening all of the sudden with HM2, TST is reading from a cached table so I would think there should never be any database lag even on a huge database

[Nekitor]

Hello! I have tried to load the same database (more than 6 millions hands, could be 10 million) to my friend`s notebook (it has 2Gb RAM instead of 1Gb) and i have the following result: the first scan is slow (400 seconds) and all other scans are ok - 50-80 for 700-1000 players.

On my old computer i have following situation: first scan can be 500-1000 econds, 2nd scan can be quick 100 seconds, 3d scan is again slow and can be slower then 1st one. So most scans are very very slow.
I did defragmentation of hard drive and most tips, that increase the productivity of HM2. I seems that it helped but not much and not for long.

Do you think it could be connected with my RAM ? or cache memory?
I am thinking how to fix my problem, maybe a computer with more RAM can help or there must be some other components better then in my computer.
Or could be other possible solutions.
Please write anything you think about the problem

[Zandry]

Well, are you saying your computer only has 1gb of ram? If that's the case then you probably could get some improvement by adding more ram. 10million hands is pretty big but it's not necessarily that huge, if you have an old computer, that could be the problem. How is the lag in other programs, like does HM2 load the HUD fast and do players data load quickly in HM2? Is TableScan the only thing which is lagging for you?

[Nekitor]

Yes there are some lags, but the HUDs usually load in 5-10 seconds, so much more problems are with TST.
I see only one decision: to load my base in HM1 and connect TST to HM1 database

[Zandry]

Do you have me on AIM/MSN/ICQ/Skype? If so could you send me a message, if not could you add me?

AIM: ZandryTST
MSN: zandry@tablescanturbo.com
ICQ: 571846001
Skype: ZandryTST