You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would be implemented later in future, but I propose a system whereby very large Bonnie config files that don't change often can have the entire Bonnie parsing system run on them and the output cached into a file like .bonnie.cache.json. We could then read directly from this file, making future command runs much faster. We could also store the bonnie.toml file's hash, allowing us to update if it changes. Right now, this isn't an issue, but if and when ordered domain execution is finalised, processing speed could become a significant issue for configurations with complex control flows.
The text was updated successfully, but these errors were encountered:
For complex control flows, regular expression parsing slows configuration parsing down significantly (around 100ms for full execution of the testing file), so this feature is now being implemented.
This would be implemented later in future, but I propose a system whereby very large Bonnie config files that don't change often can have the entire Bonnie parsing system run on them and the output cached into a file like
.bonnie.cache.json
. We could then read directly from this file, making future command runs much faster. We could also store thebonnie.toml
file's hash, allowing us to update if it changes. Right now, this isn't an issue, but if and when ordered domain execution is finalised, processing speed could become a significant issue for configurations with complex control flows.The text was updated successfully, but these errors were encountered: