View Single Post
  #2  
Old 02-10-2006, 03:20 PM
mittelhauser mittelhauser is offline
Member
 
Join Date: Dec 2004
Location: Los Gatos, CA
Posts: 40
Default Re: PokerDaVinci January BETA: semi-public release

[ QUOTE ]

Just one question:

If you were to benchmark your product on say importing and using 1 million hands or more, then how does your product compare to Poker Tracker, Poker Office and Poker Manager.

So far I found Poker Manager wins hands down in respect to this question: it is about 3-4 times faster for import than either Poker Tracker or Poker Office <u>AND</u> DB performance does not seem to degrade badly as more hands get imported [as in other products]). Extra functionality is not helpful to me, if speed issues make a product totally unusable... [img]/images/graemlins/smile.gif[/img]

The only reason I ask this is because I don't want to waste yet another 2/3 days importing hands only to find it is not what I am looking for. For me personally the DB speed is the main factor and some kind of standard benchmark would help me most in judging which product is best [img]/images/graemlins/smile.gif[/img]

Juk [img]/images/graemlins/smile.gif[/img]

[/ QUOTE ]

Juk,

I hear you. I can't give you concrete answers because I haven't taken the time to run the comps on the beta since it keeps changing. I wouldn't suggest spending 2-3 days importing a million hands into the beta since you may need to do it again w/ the February beta, etc. until the DB format is finalized for release.

Having said that, I can tell you some general "truths"...

1) The performance will be independent of the size of the file you are importing. 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. There are some bugs in the current beta which makes this statement (slightly) untrue but the next beta will resolve them. Specifically, while parsing is linear, we do things like count the number of hands in a file before we start (to provide a status bar) and this takes a *long* time if the file gets big. I need to add a method to estimate rather than count if the size of the file is big (e.g. hundreds of thousands of hands).

2) 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.

3) Last time I checked, PokerDaVinci was about 2-3 times faster than PT for small files. There is no real comparison on larger files since (as you mention), PT just goes completely to hell. I have not tested against PokerManager. Again, this isn't an "official" comparision. That will need to wait until we get closer to release but I wanted to give you an idea.

4) Finally, the beta database is not optimized for performance so it will only get better. Although this is mostly true for the queries as we build more complex indexes. The actual parsing performance probably won't change that fundamentally since it is bound by the speed of the regular expression matching.

-Jon
Reply With Quote