[jukofyork]

Thanks for the detailed answer! [img]/images/graemlins/smile.gif[/img]

I think I better wait until the Feb beta to try importing my hands (I done this for PG SQL and PM now, and it eats a few days each time... [img]/images/graemlins/smile.gif[/img] ).

[ QUOTE ]
I have no idea what the heck PT does to make it so bad when you import a large file (it seems to get exponentially worse as the file gets larger). We actually save each hand to the DB as it gets parsed so the performance is linear "O(N)" if that means anything to you.

[/ QUOTE ]

Yep, O(n) means something to me [img]/images/graemlins/smile.gif[/img] I too have no idea what the heck PT does, but it drove me crazy in the end... [img]/images/graemlins/smile.gif[/img]

[ QUOTE ]
The app is entriely multi-threaded and the DB import (e.g. parsing) is separate from the viewing of the data. In other words, unlike PT which locks up the whole app (and often the whole machine with a 95% processor usage), you can simply start to import your hands and then put it into the background while you start to view your data (or do other things). This also means that it will take advantage of things like a dual processor machine.

[/ QUOTE ]

I too have suffered from the 'lockups'. I originally re-imported all my hands into PT/PGSQL on a separate dual processor machine (it just crashed on my machine... [img]/images/graemlins/frown.gif[/img] ). It locked the whole PC for nearly 3 days for about 900k hands, used huge amount of page-file (GBs), and used just 1 processor (PG SQL barely used 5% of 2nd processor...).

I will look forward to seeing how PokerDaVinci turns out - Juk [img]/images/graemlins/smile.gif[/img]