From c73a2795ffedd6ca208915af97ea2d692f237bf8 Mon Sep 17 00:00:00 2001 From: erikjohnston Date: Fri, 26 Apr 2024 08:46:20 +0000 Subject: deploy: 0ef2315a99859217e319e4cb5a29d88a054952ff --- develop/usage/configuration/config_documentation.html | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'develop/usage/configuration') diff --git a/develop/usage/configuration/config_documentation.html b/develop/usage/configuration/config_documentation.html index c3bde7a4de..bd5801fded 100644 --- a/develop/usage/configuration/config_documentation.html +++ b/develop/usage/configuration/config_documentation.html @@ -1275,6 +1275,9 @@ for a given destination and the state of the backoff is stored in the database.<

event_cache_size

The number of events to cache in memory. Defaults to 10K. Like other caches, this is affected by caches.global_factor (see below).

+

For example, the default is 10K and the global_factor default is 0.5.

+

Since 10K * 0.5 is 5K then the event cache size will be 5K.

+

The cache affected by this configuration is named as "getEvent".

Note that this option is not part of the caches section.

Example configuration:

event_cache_size: 15K
@@ -1294,6 +1297,7 @@ set.

variable. Setting by environment variable takes priority over setting through the config file.

Defaults to 0.5, which will halve the size of all caches.

+

Note that changing this value also affects the HTTP connection pool.

  • per_cache_factors: A dictionary of cache name to cache factor for that individual -- cgit 1.5.1