This repository has been archived by the owner on Jun 15, 2024. It is now read-only.
Persistence: Decouple step-updates from flushing to disk to improve performance/resource usage #137
Labels
Comments
This was referenced Oct 16, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem
Currently, every single
:step-result-updated-event triggers flushing data to disk. This is both a performance issue (because all components sending these events block until all event-handlers processed information) and unnecessary stress on the system (because of I/O and CPU operations)Potential Solutions
Rate-limit flushing to disk
Flushing to disk can be rate-limited to a few times per second
The text was updated successfully, but these errors were encountered: