mirror of
https://github.com/fleetdm/fleet
synced 2026-05-23 00:49:03 +00:00
5e48e3d4f3
> For #26178 # Checklist for submitter ## Data from testing We tested the changes out by directly creating the index in our dogfood env. We saw a decrease in resource usage, captured in these screenshots: DB load (taller spike towards the left is without the index, subsequent spikes are after the index was added)  DB load over a longer period (overnight 2025-02-12 -> 2025-02-13)  CPU utilization  Memory usage  --- If some of the following don't apply, delete the relevant line. <!-- Note that API documentation changes are now addressed by the product design team. --> - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [x] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) - [x] If database migrations are included, checked table schema to confirm autoupdate - [x] A detailed QA plan exists on the associated ticket (if it isn't there, work with the product group's QA engineer to add it) - [x] Manual QA for all new/changed functionality
2 lines
No EOL
110 B
Text
2 lines
No EOL
110 B
Text
- Fixed an issue with increased resource usage during vulnerabilities processing by adding a
|
|
database index. |