How to Diagnose ClickHouse 'Too Many Parts' Error Before Running OPTIMIZE FINAL

·1 views

ClickHouse throws a 'Too many parts' error when insert rates outpace background merge operations, causing inserts to slow down or fail entirely. Before running OPTIMIZE FINAL, engineers should first query system.parts to identify which partitions are accumulating excessive active parts. Checking system.merge_tree_settings reveals the actual delay and throw thresholds configured on the cluster, which may differ from table-level overrides. Sampling system.merges twice in succession helps determine whether the merge backlog is shrinking or stalled. Only after diagnosing the root cause — such as frequent small inserts or a poorly chosen partitioning key — and reducing incoming write pressure should a forced merge be considered.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Nvidia Launches NeMo Switchyard to Cut AI Agent Costs via Intelligent Model Routing

Nvidia has released NeMo Switchyard, an open-source routing SDK designed to automatically direct tasks within AI agent workflows to the most cost-appropriate model. Alongside it, the company launched Nemotron 3.5 Lightning, a 30-billion-parameter open mixture-of-experts model with only 3 billion active parameters. Switchyard aims to solve a common problem in agent development: routing simpler steps to cheaper models while reserving expensive frontier models for tasks that genuinely require advanced reasoning. Nvidia claims the system can reduce costs to roughly one-third of using Claude Opus 4.8 alone, with partner Ramp reporting 58% cost savings and 33% faster runtime on internal benchmarks. These figures come from vendor and partner testing, and the system's real-world reliability will depend heavily on how well quality is evaluated alongside cost and latency.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Permissive robots.txt does not grant rights to republish scraped content

A developer audited ten websites their scraper had been collecting data from since July, applying a strict rule: only sources with explicit written licences permitting commercial reuse would qualify. Of the ten sites reviewed, only two passed — including Troy Hunt's blog, which carries a Creative Commons Attribution 4.0 licence — while eight were rejected for lacking any reuse permissions. The author notes that robots.txt only governs whether a bot may fetch a page, not whether the fetched content may be republished, and treats silence on licensing as a no. One site, Julia Evans', was excluded not on licensing grounds but on stated intent, after its robots.txt displayed a clear ASCII-art message asking AI systems to stay away. The author acknowledges that the scraper had been running for a month against non-permissive sources, and that no harm occurred only because the retrieval layer had not yet been built — describing that outcome as luck rather than a proper safeguard.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AMD partners with science ministry to build open-weight AI ecosystem

AMD announced a partnership with an unspecified government science ministry to develop an open-weight artificial intelligence ecosystem, as reported by MSN on August 11, 2026. The collaboration leverages AMD's existing open-model portfolio, including OLMo and Instella, which are trained on Instinct MI300X GPUs and freely available on Hugging Face with no commercial license restrictions. AMD's open-source software stack ROCm serves as the technical foundation offered to public and private partners as an alternative to Nvidia's proprietary CUDA platform. Governments increasingly view open AI weights as a matter of technological sovereignty, since relying on closed models ties national infrastructure to private commercial decisions. Financial terms, the specific country involved, and a project timeline were not disclosed at the time of publication.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Coinbase-Backed x402 Protocol Lets AI Agents Pay for APIs Using Stablecoins

The x402 protocol is an open, HTTP-native payment standard developed by Coinbase and now governed by the x402 Foundation, designed to enable software to pay for APIs automatically using stablecoins like USDC. It revives the long-dormant HTTP 402 Payment Required status code, embedding payments directly into standard HTTP request-response cycles rather than relying on separate billing flows. The protocol is particularly aimed at autonomous AI agents, which cannot manage traditional account signups, API keys, or subscription renewals on their own. In the x402 flow, a client requests a resource, receives payment terms from the server, submits a signed payment proof, and gains access once a facilitator verifies the transaction. The standard is open and not locked to any Coinbase product, making it applicable to a broad range of machine-to-machine and decentralized finance use cases.

0 comments Read more at DEV Community