tips:flowindextuning
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
tips:flowindextuning [2023/09/27 14:35] – created veera | tips:flowindextuning [2023/09/27 15:04] (current) – [Types and typical sizes at ISP scale] veera | ||
---|---|---|---|
Line 4: | Line 4: | ||
The Trisul flow database is a high performance high throughput store specifically designed for Network Flow storage. | The Trisul flow database is a high performance high throughput store specifically designed for Network Flow storage. | ||
- | The tuning parameters are controlled by the following section in [[trisulHubConfig.xml Trisul Hub Configuration file]|https:// | + | The tuning parameters are controlled by the following section in [[https:// |
+ | |||
+ | ===== Flow database tuning parameters ===== | ||
+ | |||
+ | <code lang=xml> | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | |||
+ | <!-- Bitmap indices - to disable set buckets to 0 --> | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | |||
+ | |||
+ | <!-- Bloom filter matrix.. set to bits and hashes to 0 to disable an index --> | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | |||
+ | </ | ||
+ | </ | ||
+ | |||
+ | |||
+ | </ | ||
+ | |||
+ | |||
+ | ===== Indices and Filters ===== | ||
+ | |||
+ | |||
+ | The main tuning are the sizes of the Bitmap Indices and Bloom Filters. The details of the implementation are not important here. We talk about the tyeps and how to disable them. | ||
+ | |||
+ | |||
+ | <note important> | ||
+ | |||
+ | ==== Types and typical sizes at ISP scale ==== | ||
+ | |||
+ | |||
+ | === Bitmap indices === | ||
+ | |||
+ | |||
+ | |kHOST_BUMPX_BUCKETS| ip address v4 and v6| 870M + 870M + 870M = 2.6G | 2.6G K1A + 2.6G K1Z + 2.6G K21= 7.8GG | | ||
+ | |kAPP_BUMPX_BUCKETS| ports | 300MB | 4G | | ||
+ | |kPROTO_BUMPX_BUCKETS| protocol | | ||
+ | |kGEN1_BUMPX_BUCKETS| router IP | | ||
+ | |kGEN2_BUMPX_BUCKETS| router Interface ingres| | ||
+ | |kGEN3_BUMPX_BUCKETS| router interface egres| | ||
+ | |kAUX0_BUMPX_BUCKETS| tag 0 | | ||
+ | |kAUX1_BUMPX_BUCKETS| tag 1 | | ||
+ | |kAUX2_BUMPX_BUCKETS| the main flow tag strings | | ||
+ | |kHOST24_BUMPX_BUCKETS| net/24 | 860M | 2.6G| | ||
+ | |kHOST16_BUMPX_BUCKETS| net/16 | 430M | 670M| | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ |
tips/flowindextuning.txt · Last modified: 2023/09/27 15:04 by veera