PokerTracker

Hi im importing 1mil hands into my new pt4, the hands are hands i bought.. All cash games

it says i have to wait 19hours and importing 19h/s (seems as time goes by it get even slower wtf?)
I get a bunch of errors as well 60k hands 500 error is that normal ?

I have postgressql 8.3 or something but i have no idea how to update it to 9.0..

Could you guys help me out so everything goes a lot faster?? (how long would it take normally??)

Why was PT3 so much faster???

Kind regards

It even slowed down to 6h/s and only imported 94k remaing time is like 49h this is unreal...

How to get this normal and working?

My computer:

Intel core i5 CPU @2.53ghz
6GB
64bit
Win7

Btw my Harddisk C: is 49gb and is running full very quickly as well for some strange reason.. Is that why its getting slow!?!?
I have moved processed files on to my other drive D:

Seems like my folder in postgresql (base) is like 12gb only from importing hand histories? Can i delete that folder to make more space or bad idea!?

Do not delete any files from your PostgreSQL folder unless you know what you are doing! The only files you can safely delete from there are in the pg_log folder - the files in your PostgreSQL folder ARE your databases and associated PostgreSQL organization files.

PT4 may appear slower than PT3 in terms of the hands per second headline figure but actually PT4 is doing all the housekeeping needed during the import, where PT3 has to do it afterwards. Overall the times should be similar.
You may find that doing one very large import can slow down towards the end and breaking up the import into sections can help with that. Fortunately this type of large import is a one-off process in nearly all cases.

That said, if your disk is nearly out of space then that will affect the performance of PostgreSQL and Windows in general.
Did you actually mean 49GB? That is pretty small for a C: drive these days and will fill up very quickly if you have Windows and other applications running on it as well as anything other than a pretty small database. Do you have other drives in this machine?

Do i need to update my postgressql 8.3 to 9.0 ?? If so how do to that ?

My C: drive 49gb total and my D: is 249gb, shall i make C: bigger with disk management??

What do you recommend doing and if so how big shall i make my C: ???

Kind regards

Are these two partitions of the same drive? I'm a bit confused as to your setup. 9.0 will work a bit better than 8.3 but unless you're also on a 64 bit machine the difference is fairly marginal.

In terms of space, our rule of thumb is 1M hands = 10G of disk space for full ring hands (6G for 6 max, 2G for heads up).

There on the same drive yes got 2 partions, well i just started with pt4 never had any problems with pt3 though...

So how to make importing faster because it goes way to slow start of by 80h then goes to 10 and it even stops after a while..

Importing appears slower in PT4 than it did in PT3 because cache time is included in PT4's import routine. The hands can appear to stall also when tournament detection is going on or tournament summaries are importing because there are no "hands" being imported (though there is still work being done).

It appeears to be slower??? No it really is slow..

It might be my computer, but i tryed to import it said before 7 hours then it said 10 then is said 49 and after a while next morning it even stopped working only importing like 74k hands instead of 1 mil..

Can you help me out with this matter or /??

In our internal tests while it appeared slower in h/sec it did not end up being slower in the full amount of time with housekeeping included.

Please restart PT4 using the logging enabled link on your Start Menu, reproduce this problem and then report it via our support system with the log file - that will help us figure out what is going on here and get it fixed for you. You can find that file by clicking File --> Show User Data Folder in the main PT4 window - the file we need is the text file called PokerTracker4 that is in that folder.

This is not a general issue affecting everyone and we do need your particular logs in order to figure out what's going wrong in your case.