"Call vs BTN Open" stat & cache/custom stats question

[Fox128]

..vs CO Open is already in there.
Call vs BTN is still missing. Just a reminder ;)


Edit: Speaking of stats, a 4bet (after rfi) and a 5bet (after 3bet obv) RANGE stat would REALLY be appreciated.

Btw what stats are more system-resource consuming? Built in one's, or their equivalent custom ones?
(might be obvious, but still want to know)
Like.. are custom stats not updating while playing, or are they, but just don't get cached? What's the difference exactly?
Do they ever get into the cache?

[funxmun]

Make a "Call vs BTN Open" please!

[kraada]

Call vs BTN Open is attached - it was intended to be added but was overlooked accidentally (in fact the column is there already so this is a cached stat!).

You can build those range stats yourself if you would like - if you look at the way the 4bet range stat is constructed, the rfi stat you want, you can duplicate and change the values as you would like.

The stats that take more time are those using custom columns. If you can build anything out of built-in columns they will be as effective as built in stats.

Custom columns are not cached - meaning they need to be calculated for each player at the time the stat is updated. As databases get larger that requires more data transfer which takes time.

Built-in columns are cached - meaning they are pre-calculated so we only need to get the current value and display it and it is then updated automatically for you as more hands are imported.

[Fox128]

Ok that's very intersting stuff, thank you...

So.. why is it not possible to "mark" custom columns to be cached? (and update database afterwards I guess). I think that would be important. Like if I built my own stat with custom columns and I figure that it's really useful (I want to keep it and always use it for the HUD) it would be good if they were cached right?

Is that something you might add in the future?

[kraada]

I don't know of any plans to allow users to enable caching on custom stats.

[Darvini]

Im suprised that custom columns arent cached anymore. Not from a technical point of view (dont know what problems it would cause) but from a users point of view. building you own columns was big part of PT3 for me. Its a big part of personalizing the HUD. Im hoping there will be some opportunity to cache custom columns later on.

Have you guys thought of making some polls here to get more user feedback?

[kraada]

The development team is aware of the requests, but it would be a significant change so it would not be a small project. The reason for the change was so that keeping the cache up to date and cache rebuilds were not something the normal user needed to do regularly.

[Lakestone]

I really think that this would be an essential update too. Whats the point of making custom stats for HUD if they are going to take minutes in the end to update? It really is frustrating!
If caching your own stats is a resolvement, then it should already have been implemented in my opinion.

[PeteX]

+1 vote from me for custom column caching feature.