Release 63
Smaller cloud bill, quieter error log: the console's background work can run on a schedule
Nothing you do in the console changes with this release. It prepares a cheaper way to run the service behind the console and removes several recurring errors from its logs.
What changed for people using Bellwether
- The service behind the console can idle between your clicks. Four small chores kept it busy around the clock: applying the Quant desk's scheduled changes, ending Guidance notes on their date, sending notifications and sending scheduled reports. They can now be triggered from outside on the same schedule, so the service works only while answering you or doing a chore.
- The switch comes later, with an alarm. This release only prepares the idle mode; whoever runs the installation turns it on afterwards, step by step, with a way back. From then on an alarm pages them if notifications or the Quant desk's changes stop being processed for a quarter of an hour.
- The Critic's note on a new order is recorded without an error. Each review of a proposed opening order was applied, but its copy for the audit log was refused by the database and logged as an error. The copy is now written by the part of the system allowed to write it, dated at the moment of the review.
- The first page after an update opens faster. The service used to spend up to forty seconds assembling its own interface description the first time it was asked after each update. It now ships with that description ready.
What you may notice
- Once the idle mode is on, notifications (a halt, an order waiting for you) may arrive up to a minute after the event instead of within seconds. Nothing else about them changes.
- Nothing in this release changes what the desk buys or sells, and no setting of yours moves.
Switched on
- Nothing is switched on by this release. The idle mode, its schedule and its alarm are turned on later by whoever runs the installation, step by step, with a way back.
Known gaps and what’s next
- The larger lines of the cloud bill (the always-on machine and the database) were not measured in this work; they are next.
- Whether a minute is too slow for notifications will be decided after a week of running that way.
Release 63 f0c38c2