Skip to content

Commit

Permalink
reduced memory (#3598)
Browse files Browse the repository at this point in the history
* reduced memory

* obsolete var
  • Loading branch information
jessegoodier authored Aug 21, 2024
1 parent 613c6c5 commit ac57b8a
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 7 deletions.
2 changes: 0 additions & 2 deletions cost-analyzer/templates/_helpers.tpl
Original file line number Diff line number Diff line change
Expand Up @@ -1111,8 +1111,6 @@ Begin Kubecost 2.0 templates
{{- end }}
- name: LOG_LEVEL
value: {{ .Values.kubecostAggregator.logLevel }}
- name: DB_COPY_FULL
value: {{ (quote .Values.kubecostAggregator.dbCopyFull) | default (quote true) }}
- name: DB_READ_THREADS
value: {{ .Values.kubecostAggregator.dbReadThreads | quote }}
- name: DB_WRITE_THREADS
Expand Down
6 changes: 1 addition & 5 deletions cost-analyzer/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2564,7 +2564,7 @@ kubecostAggregator:
# set to 0 for max partitioning (minimum possible ram usage, but the slowest)
# the default of 25 is sufficient for 95%+ of users. This should only be modified
# after consulting with Kubecost's support team
numDBCopyPartitions: 1
numDBCopyPartitions: 25

# How many threads the read database is configured with (i.e. Kubecost API /
# UI queries). If increasing this value, it is recommended to increase the
Expand All @@ -2584,10 +2584,6 @@ kubecostAggregator:
# default: 1
dbConcurrentIngestionCount: 1

# dbCopyFull: "true" can improve the time it takes to copy the write DB,
# at the expense of additional memory usages.
dbCopyFull: false

# Memory limit applied to read database and write database connections. The
# default of "no limit" is appropriate when first establishing a baseline of
# resource usage required. It is eventually recommended to set these values
Expand Down

0 comments on commit ac57b8a

Please sign in to comment.