TiKV内存参数以memory-usage-limit、 storage.block-cache.capacity 哪个参数为准？

dba远航 · 2024 年4 月 18 日 00:50

memory-usage-limit是全局的，是针对tikv整体进程的，而block-cache只是设置缓存的大小

TiDBer_yyy · 2024 年5 月 15 日 07:00

let mut limit =
                (block_cache_cap.0 as f64 / BLOCK_CACHE_RATE * MEMORY_USAGE_LIMIT_RATE) as u64;

github.com

pingcap/tidb-engine-ext/blob/raftstore-proxy/src/config/mod.rs#L3826


      
          };
          fill_cf_opts!(self.raftdb.defaultcf, flow_control_cfg);
          fill_cf_opts!(self.rocksdb.defaultcf, flow_control_cfg);
          fill_cf_opts!(self.rocksdb.writecf, flow_control_cfg);
          fill_cf_opts!(self.rocksdb.lockcf, flow_control_cfg);
          fill_cf_opts!(self.rocksdb.raftcf, flow_control_cfg);
          
          // Validate memory usage limit.
          let block_cache_cap = self.storage.block_cache.capacity.unwrap();
          let write_buffer_cap = self.rocksdb.write_buffer_limit.unwrap_or(ReadableSize(0));
          if let Some(memory_usage_limit) = self.memory_usage_limit {
              let total = SysQuota::memory_limit_in_bytes();
              if memory_usage_limit.0 > total {
                  // Explicitly exceeds system memory capacity is not allowed.
                  return Err(format!(
                      "memory_usage_limit is greater than system memory capacity ({})",
                      total
                  )
                  .into());
              }
          } else {

system · 2024 年7 月 14 日 07:01

此话题已在最后回复的 60 天后被自动关闭。不再允许新回复。