PDA

View Full Version : Problem whith scanning PS


websolo
01-16-2012, 04:33 PM
Hi!
HM2 base. PokerStars.
I having a problem whith "low speed" scanning tables. When scanning pokerstars client TableScan scrolling tables whith normal speed, but in Status display something like this:

Status
Tables: 20/225

that is first digit growing very slow, whereas second digit begin normal speed as scrolling in client.
As a result, the overall rate of scanning is obtained by very slow.

Guenni
01-16-2012, 06:28 PM
You have that problem in the beginning of your session (especially first scan) or during your session ? I'm experiencing the same, but for me it is only the first scan and the "lag" is caused by HM, not by TST as far as i tested it.

websolo
01-16-2012, 07:38 PM
The problem occurs before i start playing. Need to run PermaScan several times (4-5) to achieve normal result. And I guess it's not a HM2 problem because i was trying to scan without HM2 started. Maybe something whith postgree or network connection, in my case it's two different computers (HM2+postgree and pokerstars+tablescan)?!

Zandry
01-16-2012, 07:54 PM
My suggestion would be to restart postgres or just restart the computer where you have HM2 installed, sometimes it can start lagging and a restart fixes it up. Another thing you could try is in TableScan > Configure > Settings > Performance > Give TableScan threads highest priority, that could help if somehow the issue is on the computer with TST on it.

But most likely postgres is lagging on your other computer, I guess it could also happen if the computer you're using to scan is at near 100% cpu usage but that seems less likely. TST just reads from the cache in HM so it really should never lag like that, let me know what you find and if you're able to fix it

Guenni
01-17-2012, 09:51 AM
Uh yeah, sorry for this one. I meant Postgres/database and not HM. Just mixed this one up.

Zandry
01-18-2012, 08:50 PM
Uh yeah, sorry for this one. I meant Postgres/database and not HM. Just mixed this one up.

No problem, what you said made perfect sense to me anyways :) Thanks for trying to help :)

websolo
01-29-2012, 01:03 PM
I noticed that it comes with a large HM2 base (18Gb). If i create a new base in HM2 scan begin normal. And it does not depend on the location of the base (local or network). When i use HM 1.12 version scan begin normal always on any base size. it seems that there is a difference between HM1 and HM2 bases to scan TST.

Zandry
01-30-2012, 04:33 AM
I noticed that it comes with a large HM2 base (18Gb). If i create a new base in HM2 scan begin normal. And it does not depend on the location of the base (local or network). When i use HM 1.12 version scan begin normal always on any base size. it seems that there is a difference between HM1 and HM2 bases to scan TST.

Actually, the database query for HM1 and HM2 that tablescan uses is almost exactly the same, so I don't think there should be any difference, maybe it's because you're importing in HM2 but not in HM1 when you tested it? One thing you could try if you haven't already, is in Configure > Settings > Performance > Give TableScan Threads Highest Priority. Try turning that option on if it isn't on, and let me know if that helps any

LutiiChell
02-15-2012, 07:10 PM
I didnt encountered the problem so far, but I have a simple upload program that I can test tomorrow and let you know.
Could it be related to the file type ? What version of Service Desk ?

Zandry
02-15-2012, 07:59 PM
Sorry, I don't understand your question, maybe if you could rewrite it? I'm glad you haven't had the problem again recently :)

Also to websolo, I'm sorry I doubted you, it does seem like you are right and I was wrong, this problem seems to only be happening to people with HM2, and I never saw it with HM1, so it looks like you were right, I will try again to see if I can figure out what is happening here

websolo
02-16-2012, 06:31 AM
Unfortunately I have nothing new to report for you. But I can only repeat that the problem is not observed if the HM2 base is small. I also have a suspicion that my computer does not have enough resources. But I do not have yet another to check it.