Skip to content

chart: tune TSDB for promscale usage #616

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 28, 2022
Merged

chart: tune TSDB for promscale usage #616

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion chart/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ keywords:
- monitoring
- tracing
- opentelemetry
version: 17.4.0
version: 17.5.0
# TODO(paulfantom): Enable after kubernetes 1.22 reaches EOL (2022-10-28)
# kubeVersion: ">= 1.23.0"
dependencies:
Expand Down
11 changes: 11 additions & 0 deletions chart/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,17 @@ timescaledb-single:
# PGBACKREST_REPO1_S3_KEY_SECRET
backup:
enabled: false
# Applying tuning to TimescaleDB as per
# https://docs.timescale.com/promscale/latest/recommendations/config-recomm/#database-configuration
patroni:
bootstrap:
dcs:
postgresql:
parameters:
checkpoint_timeout: 15min
bgwriter_delay: 10ms
bgwriter_lru_maxpages: 100000
# synchronous_commit: "off"
# TimescaleDB PVC sizes
persistentVolumes:
data:
Expand Down