37 lines
4.4 KiB
Markdown
37 lines
4.4 KiB
Markdown
The metrics panel reconvened after commit `3922e28` to review the implemented base and revisit the features deferred in the original plan. The user authorized proceeding with all of them, including experiments based on limited evidence.
|
||
|
||
The base passed 711 unit tests, Svelte checking with no errors or warnings, and a production build. Firefox checks exercised combined search/sort state, preservation across range changes, pointer and keyboard chart selection, failed background refresh with retained data, successful retry, and 390px layout without page overflow. These checks caught and fixed a shallow-URL reactivity issue before the commit. Calculation parity against the previous implementation held within `1e-7` on a 118,806-row synthetic fixture. Seven-day query time fell from approximately 1,369ms to 367–408ms in the uncontended comparison.
|
||
|
||
The post-commit engineering and UX reviews found no blocking issue. Two small follow-ups were accepted: neutral copy for samples with zero elapsed time, and a polite announcement when a user selects a chart period. Background refresh should not repeatedly announce the chart.
|
||
|
||
The team revisited the original objections as design constraints:
|
||
|
||
| Feature | Original concern | Agreed experiment |
|
||
| --- | --- | --- |
|
||
| Percentage chart | Normalization hides sample volume. | Default to share of captured server time, including unknown, with an Hours switch and exact durations in the selected-period readout. |
|
||
| Fleet pressure score | Map intervals overlap and cannot be added into elapsed fleet time. | Pool full map-hours divided by known-capacity map-hours; name the denominator explicitly and show how many map groups contribute. |
|
||
| Previous-period changes | Retained and observed history may differ substantially. | Show comparisons from available samples, including both denominators and a partial-history label. Utilization changes are percentage points. |
|
||
| Activity heatmap | Sparse observations can look like stable recurring demand. | Show duration-weighted occupancy by local weekday/hour, with known/unknown time, contributing dates, and no-data cells distinct from observed zero. |
|
||
| Hosting recommendations | Occupancy and saturation do not prove unmet demand. | Generate advisory, reversible hosting experiments from visible rules. Include evidence and tentative labels; never automatically create or remove servers. |
|
||
| Global filters | Inconsistent scopes would make the page misleading. | Apply exact game/map scope to every aggregate, comparison, heatmap, recommendation, and ranking; preserve collection boundaries before filtering. |
|
||
| Historical server links | A name may have been reused for a new instance. | Label the action “Open current server” and show it only when a current registration exists. Historical totals remain grouped by name. |
|
||
|
||
The agreed hierarchy keeps the two headline cards and core timeline. Compact scope controls sit near the time-range control. Pressure, comparisons, advisory experiments, and the secondary heatmap follow the timeline so the added features do not crowd out the primary task on mobile. Use neutral comparison colors, visible units, and concise evidence next to each recommendation.
|
||
|
||
The original plan remains as the record of the initial conservative scope. These decisions supersede its deferrals; limited data does not disable a feature when a defined calculation or explicitly tentative experiment is possible. An unavailable denominator still remains unavailable rather than becoming an invented number.
|
||
|
||
All seven additions were implemented. The expanded full suite passed 731 tests;
|
||
subsequent refresh-response hardening passed its focused tests, including a new
|
||
malformed-response case. Svelte checking reported no errors or warnings and the
|
||
production build passed. Firefox exercised the percentage/Hours switch with
|
||
preserved table state, current-registration links, whole-report game/map filters,
|
||
empty scopes, heatmap keyboard selection and timezone changes, saved preference
|
||
adoption, and explicit timezone precedence. The final mobile report fits at
|
||
390px without page overflow.
|
||
|
||
The combined 30-day report took 443–446ms on the seven-day, 118,806-row fixture.
|
||
A separate full-retention fixture with six servers and 535,680 rows took
|
||
1.96–3.30 seconds for the combined 30-day report. The queries still run
|
||
synchronously; that measured full-retention cost remains an improvement target.
|
||
These local synthetic timings are not production guarantees.
|