Same hands in different DB's

[Mr Tiger]

Hi. I usually use the HUD with several DB's: one with played hands and several with mined hands. Sometimes hands in different DB's duplicate each other. Does the HUD ignore duplicate hands in different DB's? Do these duplicate hands have any influence on the HUD perfomance?

P.S. As I have read, dividing huge DB into several smaller ones leads to higher perfomance. But I think very many smaller DB's can also lead to lower perfomance (am I right?). What is the optimal DB's size?

[WhiteRider]

Hi. I usually use the HUD with several DB's: one with played hands and several with mined hands. Sometimes hands in different DB's duplicate each other. Does the HUD ignore duplicate hands in different DB's? Do these duplicate hands have any influence on the HUD perfomance?

Duplicated hands in different DBs will both be counted, so the stats will show more counts of everything. There is no (sensible) way to check for duplicates across DBs like this.

P.S. As I have read, dividing huge DB into several smaller ones leads to higher perfomance. But I think very many smaller DB's can also lead to lower perfomance (am I right?). What is the optimal DB's size?

You shouldn't have too many databases, as this requires more opening/closing/switching around. Postgres can cope with pretty big databases. I don't know any ideal sizes, but the general approach is to have one "played" DB, and rolling monthly (or whatever) observed DBs.

[Mr Tiger]

Thank you for answers, WhiteRider. Selective purge, which is going to come in the nearest updates, will help much to prevent duplicating played and observed hands :)