Luck adjusted winnings in SNGs

[Yogi Rob]

Actually, I've just realized something. The speed of the hand evaluator could be the cause of the slow import speeds for everybody. I recently imported a lot of hands at a rate of 3 hands/s. That's absurdly slow, but according to my very rough calculations it actually makes perfect sense considering the painfully slow hand evaluator.
<clip>
I do have an SSD so no hard drive to slow me down. Random fact of the day: 128MB is a very small amount of memory , it's not even 1% of 16GB which I can buy for the same price as PT3.

3h/s with a SSD just doesn't sound right. Are others seeing these speeds? With a SSD I'd expect at least 30h/s. Are you seeing this rate when importing just a few tourneys or only with a big import? What is the rate before Tournament Detection kicks in?

It's not the preflop enumerated equity calcs - that code isn't in beta yet. New code is fast - using plenty of precalc'd tables and I've optimized related areas which should yield a major import speed boost even with the added precision. Also, with enumeration the per-hand eval is much faster than monte carlo since we don't need to pull randoms.

[Zangeeph]

Actually, I've just realized something. The speed of the hand evaluator could be the cause of the slow import speeds for everybody. I recently imported a lot of hands at a rate of 3 hands/s. That's absurdly slow, but according to my very rough calculations it actually makes perfect sense considering the painfully slow hand evaluator.
<clip>
I do have an SSD so no hard drive to slow me down. Random fact of the day: 128MB is a very small amount of memory , it's not even 1% of 16GB which I can buy for the same price as PT3.

3h/s with a SSD just doesn't sound right. Are others seeing these speeds? With a SSD I'd expect at least 30h/s. Are you seeing this rate when importing just a few tourneys or only with a big import? What is the rate before Tournament Detection kicks in?

It's not the preflop enumerated equity calcs - that code isn't in beta yet. New code is fast - using plenty of precalc'd tables and I've optimized related areas which should yield a major import speed boost even with the added precision. Also, with enumeration the per-hand eval is much faster than monte carlo since we don't need to pull randoms.

I don't think others are having as slow as 3h/s.

I sent a support ticket and WhiteHall said that it is due to the size of my database (2m hands+). So I tried to import the same hands into a new database and it went at 22h/s.

However, he said that he didn't expect it to be the Tournament Detect that took so long. He thought that it should be the import part that is very slow.

Why is Tournament detect slowing down my import speeds so much in a large database?

[Zangeeph]

It may be because I am using PostgreSQL v9.0.6. Is this an incorrect version of PostgreSQL? If so how would I install the correct version without losing the database?

[kraada]

9.0.6 should work properly. Please continue to work with WhiteRider in your ticket so that we can figure out what we can do to improve the experience for you.

[Yogi Rob]

I tried selecting all of the tournaments and the 'auto detect' thing and it did absolutely nothing which is great as it took hours for 5k tourneys. The luck adj winnings is just not calculating. It sounds weird but the luck adj winnings were calculating ( even though they were wrong) before I made a main alias and now it seems the luck adj winnings haven't calculated since.

I'll have this fixed ASAP.