How can I lower Ecto repository connection costs for a low‑traffic workload?
For a low‑traffic application I want to keep the Ecto repository’s resource usage minimal while still answering requests promptly. The repository creates connection pools that can consume memory and database slots even when idle, and features such as query caching or detailed logging add overhead that may be unnecessary for infrequent workloads. I am conside