• v0.7.4 ee9e20224c

    perf(db): lower default Postgres shared_buffers 128MB->64MB across all platforms
    Release / frontend (push) Canceled after 0s
    Release / linux (amd64) (push) Canceled after 0s
    Release / linux (arm64) (push) Canceled after 0s
    Release / windows (push) Canceled after 0s
    Release / macos (push) Canceled after 0s
    Release / release (push) Canceled after 0s
    Build and Push Docker Image / build-and-push (push) Canceled after 0s

    LastSkywalker released this 2026-06-14 16:26:10 +03:00 | 194 commits to main since this release

    shared_buffers is the dominant resident-RAM lever for the managed db: it's
    a static reservation that faults into RAM as pages are touched, and for
    this app's tiny working set (a few MB of recent metrics/history) 128MB is
    oversized — it roughly doubles the steady-state db RSS for no gain.

    Drop the default to 64MB in BOTH places that define a managed db service:
    the controller generator (compose_writer.go) and the dokploy template. Both
    remain env-overridable (NODE_STATS_PG_SHARED_BUFFERS) so a large multi-host
    hub can raise them without a code change. On upgrade the controller
    regenerates compose with the new default (for nodes that never set the env
    var); new dokploy copies get 64MB out of the box. Halves the db's
    steady-state footprint (~180MB -> ~90-110MB observed) on small VPSes.

    NOTE: this is a config default, not a periodic op — a container restart's
    brief low reading is cold cache that re-warms; nothing to cron.

    Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

    Downloads