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
..
crdb	refactor(fmt): run gci on complete project (#7557)	2024-04-03 10:43:43 +00:00
v2	refactor(handler): cache active instances (#9008)	2024-12-06 11:32:53 +00:00
init.go	feat(eventstore): increase parallel write capabilities (#5940)	2023-10-19 12:19:10 +02:00
statement.go	feat(eventstore): increase parallel write capabilities (#5940)	2023-10-19 12:19:10 +02:00