corbindallas wrote:ok. what if i don't want HELuck to process all 300k of my database? i only want it to calculate between certain dates... or since certain dates?
i have to let it process all 300k hands and THEN change the filters?
do i have to have PT3 open when i run HeLuck?
edit... i'm using tourney luck not holdem luck.
Both apps calculate ALL the hands they find in the DB and calculate these hands and store the result in the database. When you run for the first time, it takes a very long time to go through all the hands. When you run it again, it only picks up new hands that were not calculated yet so it starts up much faster. Each time you change the filter, it doesn't need to calculate again since it's all in the DB already and it's very fast.
Hopefully, it'll handle your 300k hand database. If not, there's a couple of thing you can try because I don't have time to fix this right now.
1. Split up your database into smaller chunks. For example, I have my databases split into years. One database for each year. This is not only good for TourneyLuck but PT3 itself will be much more responsive with a smaller DB. You can do this by exporting all the hand histories for 2010 into one folder, all hands for 2009 into another folder etc and then creating a separate DB for each year and importing them. You would then keep the one database for 2010 as your active database.
2. If you really want all hands in the same DB, you can export all your hands somewhere and then import them into a clean database and import them in smaller chunks, like 50k at a time and refresh TourneyLuck in between chunks. I know this is a hassle, sorry. HoldemLuck already does something exactly like this when it scans database, looks at 50k hands chunks at a time but I haven't had time to make that change in TourneyLuck and it's a significant change. I don't play tourneys that much so it's never a big priority for me
Please don't nuke your original database unless you are sure you got it right. In fact, it would be a good idea to back up your database before you start this and it would probably not hurt to keep the original database around and periodicaly import new hands into it. For example, I have a database for each year but I also keep a master database that I import new hands into every few months.