PokerStars has changed the rules about what they will allow in poker tracking software and poker HUDS that their customers use. This will affect Poker Copilot. Here’s what we need to change in the next update of Poker Copilot, in order to meet the new PokerStars rules:
The HUD can’t show player icons on PokerStars and Full Tilt Poker. PokerStars states that our software “can’t rate, label, categorise, or stereotype based on tendencies.”
Our HUD colour schemes must be restricted to only two thresholds. From the examples PokerStars has given us, I interpret this to mean three colours. eg VPIP is green below 20%, yellow between 20% and 40%, red above 40%. The two thresholds are 20% and 40%.
We need to make these changes because it would be a business disaster for us if PokerStars banned Poker Copilot. All poker software companies have been given until late September to make the necessary changes.
I’ve spent the last two days working out why recent Poker Copilot updates don’t fully work on OS X 10.7. An internal component (JavaFX) used by the Session Overview is not fully supported by OS X 10.7. So the Session Overview won’t show in OS X 10.7.
As soon as you update to OS X 10.8 or higher, the Session Overview will appear again.
I’m astonished at how potential performance improvements can hide in software year after year. Today I discovered a small tweak to make Poker Copilot zoom through loading hands into your database. The improvement results in a sustained 50% increase in speed. Before the change, Poker Copilot would load about 200 hands/second. Now it is toils away at more than 300 hands/second.
In recent weeks I’ve been using an excellent developer tool called Java VisualVM to find the parts of Poker Copilot that hog the computer’s CPU, and use the most memory. Today I discovered that H2, the embedded open source database engine that Poker Copilot uses, was spending too much time analysing each SQL statement before performing it. A default performance setting was by default set too low. I set it to a much higher value, and it is like I discovered I’ve been driving up to now with the handbrake on.
(For the technically minded, and also for any H2 google searches: I increase QUERY_CACHE_SIZE to 100, instead of the default value of 8.)
The next update of Poker Copilot is due to be released this week, and will have this performance improvement, as well as some others I’ve been working on.