Read usage from sums kept as it is written, not from every request
Charts, totals and budgets summed the request table on every view. Usage is now also summed in the writing transaction into five-minute, hourly and daily tables per key, person, project and model, with latency and first-token histograms. Charts read the coarsest tier their slices allow; totals and budgets compose rows, slices, hours and days, and stay exact. Request records can be given a retention without moving any total. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
febcf251e4
commit
4454e1322c
16 files changed
+1013
-49
No files matched your search
@@ -39,6 +39,7 @@ rather than repeated.
|
||||
| `flush_interval` | `time.Duration` | [Auth](#auth) |
|
||||
| `batch_size` | `int` | [Auth](#auth) |
|
||||
| `buffer_size` | `int` | [Auth](#auth) |
|
||||
| `usage_retention` | `time.Duration` | [Auth](#auth) |
|
||||
| `name` | `string` | [Band](#band) |
|
||||
| `priority` | `int` | [Band](#band) |
|
||||
| `saturation_ceiling` | `float64` | [Band](#band) |
|
||||
@@ -367,6 +368,17 @@ BufferSize bounds the queue. Beyond it records are dropped rather than
|
||||
blocking a request: losing accounting is bad, turning a stalled database
|
||||
into an outage is worse.
|
||||
|
||||
### `usage_retention`
|
||||
|
||||
`time.Duration`
|
||||
|
||||
UsageRetention is how long the record of each request is kept: who sent
|
||||
it, which replica answered, how long it queued — what `ctl request`
|
||||
reads. Zero keeps it for ever. Totals, charts and budgets are read from
|
||||
five-minute sums kept beside the records, which are not pruned, so this
|
||||
bounds the table that grows by a row a request without changing any
|
||||
figure a page shows. At least a day when set.
|
||||
|
||||
## Band
|
||||
|
||||
### `name`
|
||||
|
||||
Reference in new issue
Block a user