skills.rest
ntk148v
ntk148vCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

altinity-expert-clickhouse-memory

Diagnose RAM usage and OOM risks in ClickHouse clusters using system metrics and query logs.

42|7|Updated Dec 26, 2025
Search Tags:#performance#memory#diagnostics#clickhouse#oom#memory-tracking
One-click install
npx skills add https://github.com/ntk148v/clicklens --skill altinity-expert-clickhouse-memory
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: altinity-expert-clickhouse-memory
Source: https://github.com/ntk148v/clicklens/tree/main/.agent/skills/altinity-expert-clickhouse-memory
Command: npx skills add https://github.com/ntk148v/clicklens --skill altinity-expert-clickhouse-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose RAM usage, memory pressure, and OOM risks in ClickHouse clusters to detect hotspots and allocation patterns.

Core Features & Use Cases

  • Comprehensive memory overview across dictionaries, tables (Memory/Set/Join engines), parts, merges, and system metrics.
  • Historical analysis and per-component breakdown to identify memory hotspots, leaks, and fragmentation.
  • Actionable guidance for memory tuning, safe configuration changes, and query patterns to reduce pressure.

Quick Start

Run the diagnostic queries included in this Skill against your ClickHouse cluster to identify memory hotspots and OOM risks.

Frequently Asked Questions about altinity-expert-clickhouse-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose ClickHouse OOM risks and high memory usage?▼

Diagnose ClickHouse OOM risks by analyzing system.asynchronous_metrics, system.dictionaries, system.tables, and query logs to surface memory hotspots, allocation patterns, and optimization opportunities.

What is causing memory pressure in my ClickHouse cluster tables?▼

Memory pressure often stems from Memory, Set, or Join engine tables, active merges, and loaded dictionaries; analyzing system tables and query logs isolates these per-component allocation hotspots.

How do I troubleshoot ClickHouse memory-related failures in production?▼

Troubleshoot production memory failures by running diagnostic queries against system metrics and query logs to identify historical allocation patterns, leaks, and fragmentation across the cluster.

Can I use this diagnostic approach for staging ClickHouse workloads?▼

Yes, you can apply these memory diagnostics to both production and staging workloads to identify memory hotspots, troubleshoot failures, and optimize configurations safely.

What's the best way to optimize ClickHouse configurations to reduce memory pressure?▼

Reduce memory pressure by analyzing per-component memory breakdowns from system tables to apply actionable guidance for memory tuning, safe configuration changes, and optimized query patterns.

Related Skills

Explore More Data & Analytics Skills→
ntk148vntk148v
42

altinity-expert-clickhouse-dictionaries

Analyze ClickHouse external dictionaries for memory usage, reload status, and performance.

Community
Advanced
ivanshamaevivanshamaev
14

starrocks-memory-tuning

Tune StarRocks memory limits, spill settings, and pool configurations to resolve query OOM and BE memory pressure.

Community
Advanced
duyetduyet

clickhouse-monitoring

Monitor ClickHouse clusters through the ClickHouse Monitor dashboard.

Community
Advanced
rnavarychrnavarych
14

role-database:capacity-planning

Estimate database storage growth and memory sizing for PostgreSQL, MySQL, MongoDB, and Redis.

Community
Advanced