Q & A Home
Customizing SNF
Errors
False Positives
Functionality
Integration
Log Files
Resellers
Result Codes
Rulebase Updates
Software
Spam
Subscriptions
Trials
Version 3 Architecture
Documentation Home
GBUdb
How does GBUdb accomodate more entries when it is just about out of space?
When more space is needed the ram allocated to GBUdb will grow to accommodate the need. This should happen infrequently. When entries are no longer active they are dropped to make room for additional entries. In practice, the GBUdb data size stabilizes quickly and then doesn't change much.
Once per day, or as otherwise specified by GBUdb condensation triggers, the GBUdb data that will be condensed. This means that all of the good and bad event counts are divided in half. This has the effect of retaining the ratios (probability of spam) while reducing the event counts (confidence figure). Any ugly entries that drop to zero are dropped from the system (forgotten). The remaining live entries are placed in a new GBUdb and the old one is thrown away. If the GBUdb size can shrink during a condensation run then it will.
