Silvan 77cd430b3a refactor(handler): cache active instances (#9008) ... # Which Problems Are Solved Scheduled handlers use `eventstore.InstanceIDs` to get the all active instances within a given timeframe. This function scrapes through all events written within that time frame which can cause heavy load on the database. # How the Problems Are Solved A new query cache `activeInstances` is introduced which caches the ids of all instances queried by id or host within the configured timeframe. # Additional Changes - Changed `default.yaml` - Removed `HandleActiveInstances` from custom handler configs - Added `MaxActiveInstances` to define the maximal amount of cached instance ids - fixed start-from-init and start-from-setup to start auth and admin projections twice - fixed org cache invalidation to use correct index # Additional Context - part of #8999		2024-12-06 11:32:53 +00:00
..
config_test.go	fix: correctly check denied domains and ips for actions (#8810)	2024-10-22 16:16:44 +02:00
config.go	feat(notification): use event worker pool (#8962)	2024-11-27 15:01:17 +00:00
flags.go	refactor(fmt): run gci on complete project (#7557)	2024-04-03 10:43:43 +00:00
start_from_init.go	feat(cmd): mirror (#7004)	2024-05-30 09:35:30 +00:00
start_from_setup.go	feat(cmd): mirror (#7004)	2024-05-30 09:35:30 +00:00
start.go	refactor(handler): cache active instances (#9008)	2024-12-06 11:32:53 +00:00