fix(api): increase memory/workers for 500-device scale, add blog post

API container was OOM-killed under 500-device mock load due to debug
logging, single worker, and 512MB limit. Bumped to info logging,
2 workers, and 1GB. New blog post documents the incident.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jason Staack
2026-03-21 07:33:35 -05:00
parent 4092806fbc
commit c9ca0d376c
3 changed files with 285 additions and 3 deletions

View File

@@ -122,6 +122,13 @@
<p class="blog-subtitle">Updates, insights, and the occasional rant about MikroTik fleet management.</p>
<ul class="blog-list">
<li>
<a href="500-devices-broke-the-api.html">
<div class="blog-list-date">March 21, 2026</div>
<div class="blog-list-title">500 Devices Broke the API</div>
<div class="blog-list-excerpt">The API container got OOM-killed under realistic load. Here's what happened, what was wrong, and how three config changes fixed it.</div>
</a>
</li>
<li>
<a href="not-posting-on-reddit.html">
<div class="blog-list-date">March 19, 2026</div>