Clustering taking too long

Experiencing technical difficulties? Think you've found a problem with PokerTracker 3? Report it here.

Moderator: Moderators

Re: Clustering taking too long

Postby snoopyyo » Sun Dec 06, 2009 10:28 am

housekeeping finally finished after 22.30 hours :-)
I was thinking about uninstalling the postgreSQL and re-installing it on my newest HD which is much faster and has way more free disk space.
But i am not comfortable doing it. (afraid of doing something wrong and losing everything) and i guess I will need ro reimport everything again, and it will take too much time again ;-)
Or is it better to try the tuning stuff first. and install the newest PostgreSQL in my old drive again? and do i need to do the housekeeping again if i stay on the same drive?
Also, what would be adviced to use as RAM. 512Mb good? or is it the more the better?
Sorry for the many questions. all help is appreciated thouh
snoopyyo
 
Posts: 13
Joined: Sat Dec 05, 2009 7:20 pm

Re: Clustering taking too long

Postby WhiteRider » Sun Dec 06, 2009 12:38 pm

If you have less than 512MB RAM then nearly everything will take considerably longer - we recommend 2GB+, but at least 1GB really.

If you have postgres on a disk drive which nothing else uses then you will get better performance because nothing else will interfere with the disk access.
To set that up you could copy your existing database across (either by files, which takes some care, or by backing up and restoring).
There are links to help you in the Database / PostgreSQL FAQ.

The recommendations for housekeeping frequency are in the FAQ and Database Management & Maintenance Guide.
WhiteRider
Moderator
 
Posts: 54017
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: Clustering taking too long

Postby tcwilson » Sun Dec 06, 2009 1:34 pm

Occasionally, PT3 will hang on me. When it does, it has the propensity to lock up my PokerStars games as it spins its wheels and eats up all my CPU. It's a pain to stumble through TaskManger and force the kill of postgres.exe(s) and stop pokertracker and go restart it.

As a work-around, I've created a single batch file -- and put a link to it in my QuickLaunch panel -- that will stop the Postgres database, kill pokertracker.exe and relaunch it immediately. I'm using it on a WinXP Pro box. If you're on XP home, you'll probably need to secure the 'tskill' command from the Internet somewhere then point the batchfile paths to it. Anyway, cut and paste the below text into a file called "BouncePokerTracker.bat" and you can bounce it in one click. And if anyone knows how to automagically close the resultant DOS window, I'd like to know, because it must be manually closed for now.

Thanks,
Todd

REM ------------------------ Begin BouncePokerTracker.bat -------------------
REM Stop PostgreSQL Database
"C:\Windows\system32\net" stop "PostgreSQL Database Server 8.3"

REM Kill the non-responsive PokerTracker.exe process
"C:\Windows\system32\tskill" PokerTracker

REM Relaunch PokerTracker (It starts PostgreSQL automatically)
"C:\Program Files\PokerTracker 3\PokerTracker.exe"
REM ------------------------ End BouncePokerTracker.bat -------------------
tcwilson
 
Posts: 3
Joined: Sun Nov 29, 2009 4:51 pm

Re: Clustering taking too long

Postby WhiteRider » Sun Dec 06, 2009 1:43 pm

If you put a line with just "exit" on the end, won't that close it?
WhiteRider
Moderator
 
Posts: 54017
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: Clustering taking too long

Postby tcwilson » Sun Dec 06, 2009 2:09 pm

Sounds easy enough, but no.

The pokertracker.exe is still running. The next command in the batch file -- 'exit' -- doesn't run until Pokertracker.exe is done, i.e., exits. So the dosbox never executes anything after the pokertracker.exe command.

I'm glad a moderator asked that. I was worried I'd get yelled at for posting in the wrong thread or something. I'm very scared of forums.
tcwilson
 
Posts: 3
Joined: Sun Nov 29, 2009 4:51 pm

Re: Clustering taking too long

Postby tcwilson » Sun Dec 06, 2009 2:47 pm

Figured it out. Difference is the "start" command where it launches the new session. For some reason, the quotation marks must follow the drive-letter designation and not *include* the drive-letter designation. I've been trying to figure out how to close the dos window like this for years. New file below; hope it helps somebody. Back to poker.

REM ------------------------ Begin BouncePokerTracker.bat -------------------
REM Stop PostgreSQL Database
"C:\Windows\system32\net" stop "PostgreSQL Database Server 8.3"

REM Kill the non-responsive PokerTracker.exe process
"C:\Windows\system32\tskill" PokerTracker

REM Relaunch PokerTracker (It starts PostgreSQL automatically)
start c:"\Program Files\PokerTracker 3\PokerTracker.exe"

REM ------------------------ End BouncePokerTracker.bat -------------------
tcwilson
 
Posts: 3
Joined: Sun Nov 29, 2009 4:51 pm

Re: Clustering taking too long

Postby WhiteRider » Sun Dec 06, 2009 3:01 pm

That's odd, but hey - if it works.. ;)
Don't worry about what you post - we're here to help.
WhiteRider
Moderator
 
Posts: 54017
Joined: Sat Jan 19, 2008 7:06 pm
Location: UK

Re: Clustering taking too long

Postby snoopyyo » Sun Dec 06, 2009 7:46 pm

I have 2gig RAM in my computer. but if i choose to give 2 RAM to the tuning of the postgreSQL, will my computer be slowwer? or doesn't it matter.
If it does, i will buy 2GIG RAM extra. so i can use 2 gig only for the postgreSQL
This computer lingo is like chinese for me :shock:
snoopyyo
 
Posts: 13
Joined: Sat Dec 05, 2009 7:20 pm

Re: Clustering taking too long

Postby woopwoop » Sun Dec 06, 2009 8:00 pm

snoopyyo wrote:I have 2gig RAM in my computer. but if i choose to give 2 RAM to the tuning of the postgreSQL, will my computer be slowwer? or doesn't it matter.
If it does, i will buy 2GIG RAM extra. so i can use 2 gig only for the postgreSQL
This computer lingo is like chinese for me :shock:


In my experience postgresql will use that 2gb of ram that you give it. Thus leaving your other ram needs over to the windows virtual memory which is a lot slower (as it reads and writes data on your HDD in mb/s instead of RAM in gb/s).
I'd follow the guidelines for alotting RAM to the postgresql service (see the stickies).
woopwoop
 
Posts: 50
Joined: Tue Oct 13, 2009 3:28 pm

Re: Clustering taking too long

Postby archimede22 » Thu Dec 24, 2009 9:15 am

OK guys, I know this post is dead since dec. the 6th, but I think I don't need to start a new one, since my problem is exacly the same as OP.

The reason why I post, is that maybe all the answer I need is already here, but I'm a total dummy with computer stuff. So half of what you said in here is total nonsense to me. And I'm Frensh on top of that... :(

So, I'm sure that if I am in that situation, others might as well. My request is, if possible, somedody that can help me with an easy step-by-step to get me out of my misery.

OK so, maybe you might need a few info about my computer. Here it is :

I have 115Go free space outta 286Go;
My antivirus is AVG;
I have the last version of PostgreSQL and PokerTracker, bought it two months ago;
Processor : AMD Athlon (tm) 7550 Dual-Core Processor 2.50GHz
3.00Go of RAM
My computer make a defrag. every week.

If you need something else, tell me.


Now, what I did until now is : I import 5 million hands and ask for the complete houskeeping. So the import took 48 hours and a few minutes. I almost turn crazy. Then the housekeeping start, and for another 48 hours it was the clustering that was on. I turn crazy and shutdown my computer. I couldn't take it anymore. I decide to try PT on FTP without clustering, but it didn't work well at all. So I start the clustering again, and now it's been more than 68 hours!! Since I start it, my computer run TERRIBLY slow, sometimes an Internet page can take as long as 15 minutes to load, Ctrl+Alt+Del don't work anymore. I'm out of ressource here. Nothing run well anymore and there's a couple of other simple operations or tasks that I can't do anymore.


Please, pretty big freaking please : HHHEEEELLLLPPPPPP!!!! 68 HOURS!! :lol: I'm turning insane!!

THX!
archimede22
 
Posts: 4
Joined: Tue Sep 29, 2009 3:33 am

PreviousNext

Return to Technical Support / Bug Reports [Read Only]

Who is online

Users browsing this forum: No registered users and 15 guests

cron