Write the decision before changing the system
This guide is a planning exercise for an application operator. It does not represent a PrivacyNodes deployment, support action or measured customer result. Count web processes, worker processes, migration tools and their maximum pool sizes. The sum, not the quiet average, is the potential connection demand on the database.
Rehearse the change with controlled inputs
Reserve headroom for administration and recovery work. Set pool limits before adding worker concurrency, and observe waiting time and useful completions instead of treating a larger connection count as capacity.
Use synthetic requests and test identities while checking the change. Do not expose secrets or customer data in a command, log excerpt or support note.
Verify the outcome and record the remaining limit
Run a synthetic overlap of API traffic, worker work and a deployment. Record the limit reached and the behavior that triggers a scale, queue or architecture review.
Capture UTC time, artifact or configuration revision, redacted symptoms and the next owner.
Official reference
This source was reviewed for the technical boundary in this guide; it does not document a PrivacyNodes test or provider capability.