Repository navigation
Blackwall 2.0.3
The RAM safety stop no longer fires on a dip of a few seconds. What is measured and the board.json schema are unchanged.
Fixed
- A short dip in free RAM no longer unloads the model. The guard checked once every five seconds and unloaded the model the first time free RAM was under 8 GB. A run on a busy desktop was stopped seven times in a day by dips that were over in seconds (a compile, a browser), each one costing every request in flight and a reload. Free RAM now has to stay under the floor for 45 seconds before the run stops.
- A memory stop is retried within minutes, not after ten. The cause is over long before that, and the next session waits for room anyway. A run that stopped for memory no longer counts toward the same-questions-failed limit either.
Added
- Dips are written down with their cause. The first reading of every dip records the programs holding the most memory (processes of one name summed) as a
memory lowevent in the run's log, so the next stop names what caused it.