Repository navigation
docs(sensitive): Paperless-ngx's acceptance on trinity (#133) - #700
Merged
Merged
Conversation
Measured under a synthetic backlog (five one-page scans and one of 50 pages, 300 dpi, image-only): memory.peak 1716 MiB of 3072m with no OOM kill, 3.0 cores at the busiest minute and 0.2 s throttled, 3 min 54 s for the 50 pages, and Vaultwarden through Caddy never slower than 19 ms. Both limits stand. The test documents were deleted afterwards. Refs #133 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Gerrrt
force-pushed
the
gerrrt/paperless-ngx-sensitive-14d2cb
branch
from
September 28, 2026 20:57
f3755c2 to
de75516
Compare
This was referenced Sep 28, 2026
Gerrrt
added a commit
that referenced
this pull request
Sep 28, 2026
…is deleted (#133) (#702) 20260928T203415Z held the five one-page acceptance documents. It is removed from trinity and oracle; 20260928T204939Z, taken after the cleanup, was checked identical on both sides first. Corrects the #700 entry. Refs #133 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
14 of 27 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Records the acceptance #133's 2026-09-19 correction asked for:
cpus: 4andmem_limit: 3072mmeasured ontrinityunder a scan, not just stated.What was measured
A synthetic backlog, chosen over real paperwork so nothing personal went through the archive: five one-page scans and one 50-page scan, 300 dpi, image-only and noised. Cgroup and latency samples were taken every 1–2 s.
memory.peakoom_killBoth limits stand.
THREADS_PER_WORKER=3does the limiting, andcpus: 4is only the backstop. Memory is kept, not cut, on one sample. The one-monthcontainer_memory_rssre-derivation still applies.Things worth knowing
STACK=sensitive make backupfrom another session interrupted the first run 90 seconds into the 50 pages. The file stayed inconsume/and was consumed from scratch after the restart, so the numbers come from fresh cgroup counters. That backup,20260928T203415Z, holds the five one-page test documents in itspaperless-mediaarchive. They are synthetic text and harmless, but that archive's library isn't empty.media/were removed by hand and the index rebuilt.document_sanity_checkerreports no issues, the library holds 0 documents andconsume/is empty.make validateontrinityfails one check unrelated to this change:backup-offsite.sh --self-test, case "a DEST under /tmp is refused"./tmpon trinity is itself a tmpfs, so the tmpfs refusal fires first. Everything else passes.This changes docs and comments only (
docs/changelog.md,stacks/sensitive/README.md,stacks/sensitive/compose.yaml) and needs no redeploy.Refs #133
🤖 Generated with Claude Code