ja
54ab23dce9
- Created crash analysis for 2026-03-17 OOM event. - Documented stability test results and memory tuning effects. - Added PARA-structured workflows for EOD protocol. - Updated workstation health report for current 16GB swap status.
14 lines
740 B
Markdown
14 lines
740 B
Markdown
# Next Steps - 2026-03-17
|
|
|
|
## High Priority
|
|
- [ ] Monitor system behavior under multi-day sustained load to ensure `zswap` and `MGLRU` keep the system responsive.
|
|
- [ ] Verify that `archlinux-keyring-wkd-sync.service` failure is resolved or investigate further (currently noted in health report).
|
|
|
|
## Optimization
|
|
- [ ] Evaluate if `systemd-oomd` is aggressive enough for interactive desktop use; if not, consider testing `earlyoom` as an alternative.
|
|
- [ ] Automate periodic S.M.A.R.T. checks via a systemd timer (currently manual).
|
|
|
|
## Infrastructure
|
|
- [ ] Consolidate Ansible variables for Docker memory limits into `ansible/vars/main.yml`.
|
|
- [ ] Extend `scripts/maintenance.sh` to include a summary of the last 24h OOM events (if any).
|