# Processes Published articles for Processes. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The User Write Lock: an Alternative to Transactions for Google App Engine DevFeed: [The User Write Lock: an Alternative to Transactions for Google App Engine]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-06-20T22:00:00Z Content type: tutorial Language: en Sources: [Khan Academy]() Topics: [Transactions](), [Databases](), [Google]() Tags: [caching](), [databases](), [engineering](), [google](), [infrastructure](), [news](), [processes](), [retry](), [transactions]() ### AI overview This developer article explains how transactions in Google App Engine's datastore provide atomicity for single-entity and multi-entity writes, but can introduce frozen datastore state, retries, idempotence requirements, and restrictions on datastore queries. It presents the User Write Lock as an alternative, although the supplied text ends before describing that alternative. ### Source excerpt By Craig Silverstein Transactions are the standard method in Google App Engine's datastore -- as in many databases ... Read more ## Linux server performance: Is disk I/O slowing your application? DevFeed: [Linux server performance: Is disk I/O slowing your application?]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-09-12T16:11:54Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Linux](), [IO](), [Server](), [Command-line interface](), [Processes](), [NVMe]() Tags: [blog](), [command-line](), [cpu](), [linux](), [load](), [mysql](), [nvme](), [performance](), [processes](), [request](), [server](), [ssd](), [storage](), [sysadmins](), [terminal]() ### AI overview This tutorial explains how disk I/O bottlenecks can cause high Linux load averages even when CPU usage is low. It shows how to use top, atop, and iotop on a LEMP web server, including per-core I/O wait measurements, to identify storage-related application slowdowns. ### Source excerpt If your Linux server is bogged down by disk I/O, your first step may often be to use the top command in the terminal to check load averages. Continue reading... ## Quiz: The subprocess Module: Wrapping Programs With Python DevFeed: [Quiz: The subprocess Module: Wrapping Programs With Python]() Original publisher: [Read original article]() Author: Real Python Published: 2026-09-11T12:00:00Z Content type: article Language: en Sources: [Real Python]() Topics: [Python](), [Processes](), [Streams](), [Bash](), [Exception]() Tags: [code](), [exception](), [processes](), [python](), [streams](), [tutorial]() ### AI overview An interactive 13-question quiz testing understanding of Python's subprocess module, including launching external programs, handling exit codes and failures, preventing hangs with timeouts, and working with standard streams. ### Source excerpt Test your understanding of Python's subprocess module. Run shell commands, handle exit codes and timeouts, and work with standard streams. ## OpenTelemetry proposes environment variables for context propagation across processes DevFeed: [OpenTelemetry proposes environment variables for context propagation across processes]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-09-11T11:01:22Z Content type: article Language: en Sources: [Blog on OpenTelemetry]() Topics: [context](), [tracing](), [OpenTelemetry](), [Processes](), [CI/CD](), [data-processing]() Tags: [ci-cd](), [data-processing](), [environment-variables](), [opentelemetry](), [processes](), [spans](), [tracing](), [w3c]() ### AI overview The OpenTelemetry Specification has a release candidate for using environment variables to carry trace context and baggage between processes. The article explains how this can connect spans across workflow runners, shells, build tools, test processes, and similar workloads when protocol headers or message metadata are unavailable, and requests feedback before the specification becomes Stable. ### Source excerpt A trace does not always cross a network boundary. A workflow runner starts a shell, the shell launches a build tool, and the build tool starts test processes. Batch and data-processing systems create similar chains of child processes. Without a shared way to pass trace information across these boundaries, spans from each process can end up in separate traces. If context propagation is new to you, it is the mechanism that carries information from one service or process to the next. For tracing, this includes the trace and span identifiers that let new spans join the same trace. It can also carry baggage: application-defined key-value pairs that are passed to downstream work. ## Today I will... find hidden latency across a distributed .NET application DevFeed: [Today I will... find hidden latency across a distributed .NET application]() Original publisher: [Read original article]() Author: Justin Yoo Published: 2026-09-08T16:00:22Z Content type: tutorial Language: en Sources: [Visual Studio Blog]() Topics: [.NET](), [Processes](), [GitHub Copilot]() Tags: [copilot](), [github-copilot](), [github-copilot-profiler-agent](), [latency](), [net](), [performance](), [processes](), [productivity](), [profile](), [visual-studio](), [visual-studio-2026](), [visual-studio-profiler]() ### AI overview A Visual Studio profiling walkthrough for finding hidden latency in a distributed .NET application by isolating the process responsible for a slow interaction and determining whether it is computing or waiting. ### Source excerpt When a distributed application feels slow, the user sees one delay. The code behind that delay may run across a web frontend, backend services, databases, and external APIs. If you profile only the frontend while the backend is slow, the profiler can show that the frontend is healthy without revealing the actual bottleneck. This article [...] The post Today I will... find hidden latency across a distributed .NET application appeared first on Visual Studio Blog. ## Devenv 2.3: Portless and TUI configuration DevFeed: [Devenv 2.3: Portless and TUI configuration]() Original publisher: [Read original article]() Author: domenkozar Published: 2026-09-07T13:59:38Z Content type: release Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [Pingora](), [Text-based user interface](), [proxy](), [Processes](), [configuration]() Tags: [announcements](), [configuration](), [docker](), [llms](), [localhost](), [open](), [pingora](), [processes](), [proxy](), [python]() ### AI overview Devenv 2.3 introduces an opt-in localhost proxy using Pingora for stable process URLs, configurable TUI settings, a dotenv parser, improved process cleanup, credential helpers in SecretSpec 0.20, and a smaller devenv closure. ### Source excerpt The new opt-in localhost proxy (using Pingora) gives your processes stable URLs, even when automatic port allocation changes the underlying port: { pkgs, config, ... }: { process.proxy.enable = true; processes.web = { exec = "${pkgs.python3}/bin/python -m http.server $PORT"; ports.http.allocate = 8000; env.PORT = builtins.toString config.processes.web.ports.http.value; }; } Run devenv up and open http://web..localhost. You can override hostnames per process or port and enable HTTPS per process. The TUI now has a personal configuration file for statusline placement, colors, keybindings, and log behavior. You can also hide the statusline or disable the (devenv) prompt prefix. Other highlights: multiverse.pins resolves multiple package versions through the fewest nixpkgs revisions. A new dotenv parser supports quotes, multiline values, variable substitution, and ordered files. SecretSpec 0.20 adds Git and Docker credential helpers and five new providers. Process shutdown and cleanup are more reliable. The devenv closure shrank from 528 MB to 376 MB. nixpkgs PR devenv devenv 2.3: Portless and TUI configuration Fast, Declarative, Reproducible, and Composable Developer Environments using Nix. LLMs have been used 1 post - 1 participant Read full topic ## Stop runtime threats with Workload Protection response actions DevFeed: [Stop runtime threats with Workload Protection response actions]() Original publisher: [Read original article]() Author: Théo Putegnat; Taylor Overturf Published: 2026-09-04T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [Processes](), [Vulnerabilities]() Tags: [datadog-agent](), [processes](), [security](), [threat-detection](), [vulnerabilities](), [workload-protection]() ### AI overview Datadog Workload Protection adds automated and manual runtime response actions. Agent rules can terminate matching malicious processes automatically, while analysts can investigate signals and respond manually. ### Source excerpt When a runtime threat appears, every step costs time. Datadog Workload Protection can now kill processes and isolate workloads with automated and manual response actions. ## Critical remote code execution in vm2, a widely used Node.js sandbox library DevFeed: [Critical remote code execution in vm2, a widely used Node.js sandbox library]() Original publisher: [Read original article]() Author: Daniel Abeles Published: 2026-09-02T00:00:00Z Content type: news Language: en Sources: [GitLab]() Topics: [vulnerability](), [Node.js](), [configuration](), [Threat Research]() Tags: [ai](), [containers](), [node-js](), [processes](), [sandbox](), [security](), [security-labs](), [threat-research](), [update](), [vulnerability]() ### AI overview GitLab reports a critical vm2 sandbox escape that can enable remote code execution. Version 3.11.7 blocks the reported attack, but the article advises hardening require.root and context settings and avoiding vm2 for truly untrusted code. ### Source excerpt GitLab's Threat Research Group found a critical sandbox escape vulnerability in vm2, one of the most widely adopted Node.js sandboxing libraries. The vulnerability uses a configuration copied straight from vm2's own README. We found the flaw, rated CVSS 3.1: 10.0, critical, using our own AI automated tools. Anyone running vm2 Version 3.11.6 or earlier with require.external turned on should treat this as directly exploitable. Once we found the vulnerability, we verified GitLab does not use vm2. We also reported it privately to vm2 and the maintainer fixed it fast, in vm2 Version 3.11.7. When we tested that fix again, it blocked the exact attack we reported. For anyone relying on vm2, it's worth flagging that there's a broader configuration risk here that goes beyond this one patch, based on the maintainer's own description of the fix. TL;DR Critical vulnerability: GitLab's Threat Research Group discovered a critical sandbox escape (CVSS 3.1: 10.0) in vm2, a widely used Node.js sandboxing library, which allows for remote code execution. The root cause: The vulnerability stems from default configurations found in the library's own "Quick Examples" README, where the sandbox fails to properly isolate itself from the host system, allowing malicious code to gain unrestricted access. Fix limitations: While updating to Version 3.11.7 blocks the specific attack reported, it does not fully resolve the underlying configuration risk; developers remain vulnerable if they continue to use require.external with overly broad require.root settings. Immediate recommendations: Users should update to Version 3.11.7, but must also manually harden their configurations by restricting require.root to only necessary files and setting context: 'sandbox' instead of relying on the default 'host' setting. Long-term advice: Due to vm2's history of recurring sandbox escape bugs, it is recommended to avoid using it for isolating truly untrusted code and instead opt for more robust methods like conta ## The Engineering Manager's role is under attack (again) DevFeed: [The Engineering Manager's role is under attack (again)]() Original publisher: [Read original article]() Author: Anton Zaides Published: 2026-09-01T06:01:00Z Content type: opinion Language: en Sources: [Manager.dev]() Topics: [Development](), [Artificial Intelligence](), [Large Language Model](), [Software](), [Meta]() Tags: [agents](), [ai](), [engineering-manager](), [llms](), [meta](), [organizational](), [processes](), [software]() ### AI overview A commentary on the erosion of the Engineering Manager role as companies flatten organizations and expect managers to manage larger teams while also shipping code. It argues that AI-related efficiency claims may reinforce a cycle of reduced management capacity and value. ### Source excerpt The erosion of the EM role ## What is a Neki router? DevFeed: [What is a Neki router?]() Original publisher: [Read original article]() Author: Ahmed Darwich Published: 2026-09-01T00:00:00Z Content type: article Language: en Sources: [Blog -- PlanetScale]() Topics: [Databases](), [Processes]() Tags: [architecture](), [database](), [engineering](), [neki](), [postgres](), [processes](), [scale](), [sql]() ### AI overview Neki routers sit between applications and Postgres, routing and coordinating queries across sharded database instances while handling client connections independently of Postgres backend processes. ### Source excerpt A Neki router gives applications a Postgres connection to one database while planning and coordinating queries across the shards behind it. ## Community updates: taking time off, AI club, and next events 💬 DevFeed: [Community updates: taking time off, AI club, and next events 💬]() Original publisher: [Read original article]() Author: Luca Rossi Published: 2026-08-28T07:01:45Z Content type: article Language: en Sources: [Refactoring]() Topics: [sessions](), [Artificial Intelligence](), [Processes](), [legacy]() Tags: [ai](), [community](), [events](), [ownership](), [processes](), [projects](), [sessions](), [slack]() ### AI overview A community update recaps discussions from the August Mastermind and AI Club, including planning time off without disrupting team ownership, AI learning and legacy migrations, and upcoming events. ### Source excerpt A special edition focused on our community activities! ## The lingering legacy of 'reserved' ports DevFeed: [The lingering legacy of 'reserved' ports]() Original publisher: [Read original article]() Author: George Michaelson Published: 2026-08-27T23:29:48Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Protocol (disambiguation)](), [Network](), [Process](), [Operating system](), [Unix](), [ssh](), [Firewall](), [Internet]() Tags: [dns](), [firewall](), [history](), [internet](), [network](), [ntp](), [opinion](), [process](), [processes](), [ssh](), [systems](), [tech-matters]() ### AI overview An exploration of why reserved TCP and UDP ports persist, tracing conventions such as ports 22, 53, 80, and 443 to early Internet services on multi-user systems. It explains the relationship between ports, protocol-specific daemons, operating-system administration, and modern firewall and service-discovery practices. ### Source excerpt Modern service discovery mechanisms increasingly allow services to run on arbitrary ports, yet DNS may remain the one protocol that cannot fully escape its dependency on the long-established convention of port 53. ## Python 3.15 Preview: Sampling Profiler DevFeed: [Python 3.15 Preview: Sampling Profiler]() Original publisher: [Read original article]() Author: Bartosz Zaczyński Published: 2026-08-26T14:00:00Z Content type: tutorial Language: en Sources: [Real Python]() Topics: [cpu](), [Processes](), [dashboards]() Tags: [concurrency](), [cpu](), [graphs](), [processes](), [profile](), [python](), [tracing](), [tutorial]() ### AI overview A tutorial previewing Python 3.15's new low-overhead sampling profiler. It covers profiling scripts, modules, threads, async tasks, and live processes, with CPU/I/O/GIL modes and outputs such as flame graphs, heatmaps, and a terminal dashboard. ### Source excerpt Explore Python 3.15's new sampling profiler and learn low-overhead profiling of scripts, threads, and live production processes. ## What else runs on your Postgres server, and how do we stop it from taking the database down? DevFeed: [What else runs on your Postgres server, and how do we stop it from taking the database down?]() Original publisher: [Read original article]() Author: Kaushik Iska Published: 2026-08-21T14:11:30Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [Database](), [Availability](), [Processes](), [Server](), [Monitoring](), [Go Language](), [systemd]() Tags: [availability](), [backup](), [cpu](), [database](), [go](), [logging](), [memory](), [metrics](), [monitoring](), [postgres](), [process](), [processes](), [prometheus](), [server](), [systemd]() ### AI overview ClickHouse Managed Postgres isolates supporting services with runtime budgets and cgroup v2 limits so leaks, CPU saturation, and memory pressure do not compromise database availability. ### Source excerpt ClickHouse Managed Postgres uses runtime budgets, cgroup limits, and disk-full session exemptions to keep supporting services from compromising database availability. ## Why agentic AI starts with legacy modernisation DevFeed: [Why agentic AI starts with legacy modernisation]() Original publisher: [Read original article]() Author: Suzanne Angell Published: 2026-08-21T09:33:00Z Content type: opinion Language: en Sources: [Scott Logic]() Topics: [Artificial Intelligence](), [AI Agent](), [legacy](), [legacy systems](), [data](), [Processes]() Tags: [agentic-ai](), [agents](), [ai-agents](), [artificial-intelligence](), [data](), [governance](), [integration](), [legacy](), [legacy-modernisation](), [operational-risk](), [processes](), [risk-management]() ### AI overview The article argues that organisations must address fragmented data, brittle processes, and outdated architectures before they can realise the full value of agentic AI. It explains that legacy systems may remain operationally critical, while accumulated technical, process, and organisational debt can prevent agents from accessing reliable information and executing workflows consistently. ### Source excerpt Organisations are increasingly excited by the potential of agentic AI, but many overlook the legacy obstacles that stand in the way. In this post, I explore why successful AI adoption depends on tackling fragmented data, brittle processes and outdated architectures, and why modernisation is often the most important step towards unlocking value from intelligent agents. ## Understand memory management in Amazon RDS for PostgreSQL to avoid out of memory DevFeed: [Understand memory management in Amazon RDS for PostgreSQL to avoid out of memory]() Original publisher: [Read original article]() Author: Ankita Singh Published: 2026-08-19T22:21:10Z Content type: tutorial Language: en Sources: [AWS Database Blog]() Topics: [PostgreSQL](), [Memory Leaks](), [Processes](), [Linux](), [Monitoring](), [Amazon Web Services](), [Availability]() Tags: [advanced-300](), [amazon-aurora](), [amazon-cloudwatch](), [amazon-rds](), [availability](), [aws](), [memory](), [monitoring](), [postgresql](), [postgresql-compatible](), [processes](), [production](), [rds-for-postgresql](), [technical-how-to]() ### AI overview A practical guide to PostgreSQL memory management on Amazon RDS for PostgreSQL and Amazon Aurora PostgreSQL. It explains how memory is allocated, how memory-intensive queries and diagnostic signals can be identified, and how to diagnose, prevent, and recover from out-of-memory events and excessive disk spilling. ### Source excerpt PostgreSQL out-of-memory (OOM) events and excessive disk spilling are among the most common production incidents on Amazon RDS for PostgreSQL and Amazon Aurora PostgreSQL. Learn how PostgreSQL allocates and consumes memory, how to identify memory-intensive queries, and how to diagnose, prevent, and recover from OOM events on both engines. ## A revisit of remote Spectre attacks on Cloudflare Workers DevFeed: [A revisit of remote Spectre attacks on Cloudflare Workers]() Original publisher: [Read original article]() Author: Albert Pedersen Published: 2026-08-19T16:00:28Z Content type: article Language: en Sources: [Cloudflare Blog]() Topics: [vulnerability](), [Processes](), [out-of-process]() Tags: [attacks](), [cloudflare](), [cloudflare-workers](), [edge](), [javascript](), [linux](), [memory](), [processes](), [remote](), [research](), [sandbox](), [security](), [vulnerabilities]() ### AI overview Cloudflare reassessed remote Spectre attacks against Workers and found that a limitation in Dynamic Process Isolation allowed reliable data leakage in production. The attack is already mitigated through improved isolation measures, including the V8 Sandbox and in-process isolation. ### Source excerpt In 2024 and 2025, we reassessed remote Spectre attacks on our Workers infrastructure. We share details about the new attack primitives like Spectre gadgets, remote timers, achieving co-location and how new defenses further harden Cloudflare Workers. ## A Guide to Linux /proc Filesystem DevFeed: [A Guide to Linux /proc Filesystem]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-08-17T10:34:50Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Linux](), [Kernel](), [Processes](), [cpu](), [Network]() Tags: [blog](), [cpu](), [desktop](), [examples](), [filesystem](), [guide](), [kernel](), [linux](), [network](), [process](), [processes](), [server](), [sysadmins]() ### AI overview A practical guide to the Linux /proc virtual filesystem, explaining how it exposes live kernel state such as running processes, memory, CPU information, network statistics, and hardware details. It also describes how standard tools read this data and introduces useful files and per-process directories. ### Source excerpt The /proc filesystem is a live window into the Linux kernel: process state, memory layout, CPU counters, network stats, and writable kernel tunables, all accessible with nothing but cat and grep. This guide walks through the most useful files and per-process directories with practical examples. Continue reading... ## Cutting the Noise. DevFeed: [Cutting the Noise.]() Original publisher: [Read original article]() Author: David Pereira Published: 2026-08-13T12:29:59Z Content type: opinion Language: en Sources: [Untrapping Product Teams]() Topics: [meetings](), [Processes]() Tags: [focus](), [meetings](), [processes](), [progress](), [simplify](), [workflow]() ### AI overview This opinion article argues that professional growth can come from "adding by subtracting": questioning routines, processes, meetings, and other work practices that no longer serve their original goals. It identifies predictability and stability as factors that can reduce progress and innovation. ### Source excerpt What can you stop doing now? ## Forensic container checkpointing on Amazon Elastic Kubernetes Service (Amazon EKS) DevFeed: [Forensic container checkpointing on Amazon Elastic Kubernetes Service (Amazon EKS)]() Original publisher: [Read original article]() Author: Varun DeviReddy Published: 2026-08-12T17:38:15Z Content type: tutorial Language: en Sources: [Containers]() Topics: [incident]() Tags: [advanced-300](), [amazon-eks](), [amazon-elastic-kubernetes-service](), [api](), [container-security](), [containers](), [incident-response](), [kubernetes](), [memory](), [processes](), [security](), [technical-how-to]() ### AI overview This tutorial explains how to preserve volatile runtime evidence from suspicious containers on Amazon EKS by using the Kubelet Checkpoint API. It deploys a checkpoint agent that captures container state without stopping the workload, packages the result as an OCI image, and stores it in Amazon ECR for later forensic analysis. ### Source excerpt Amazon EKS 1.34 makes the Kubelet Checkpoint API functional, so you can capture a running container's full state (memory, processes, and network connections) without stopping the workload. This post shows how to deploy an unprivileged checkpoint agent that stores forensic checkpoints in Amazon ECR as OCI images for later analysis. ## How Zapier transformed core marketing processes with ChatGPT Work DevFeed: [How Zapier transformed core marketing processes with ChatGPT Work]() Original publisher: [Read original article]() Published: 2026-08-10T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [ChatGPT](), [Processes](), [dashboards](), [Optimization]() Tags: [building](), [chatgpt](), [executive](), [optimization](), [processes](), [qa](), [qc](), [quality-assurance](), [quality-control](), [sales](), [work]() ### AI overview Zapier's enterprise marketing team uses ChatGPT Work to automate lead-funnel QA/QC, identify and fix lead problems, build campaign assets, and report recurring pipeline issues. The system reduces manual effort, accelerates campaign execution, and helps generate pipeline value for sales. ### Source excerpt The enterprise marketing team at Zapier uses ChatGPT Work to reduce the number of drop-offs in its lead funnel, build campaign assets, and automate reporting. ## Devenv 2.2: attach to running processes and persistent out-of-tree environments DevFeed: [Devenv 2.2: attach to running processes and persistent out-of-tree environments]() Original publisher: [Read original article]() Author: domenkozar Published: 2026-07-29T13:54:52Z Content type: release Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Processes](), [Text-based user interface](), [Shell](), [Automation](), [Cache]() Tags: [announcements](), [automation](), [cache](), [processes](), [terminal]() ### AI overview Devenv 2.2 adds the ability to attach to an existing process manager from another terminal, with status, ports, recent logs, and live updates. The release also includes persistent local and remote environments, shell activation improvements, SecretSpec and Cachix integration, lower idle CPU usage in the TUI, evaluation cache and automation improvements, and bug fixes. ### Source excerpt devenv 2.2 is here. You can now run devenv up -d in another terminal and in another devenv processes atttach to the existing process manager, with current status, ports, recent logs, and live updates. Other highlights: Persistent local and remote --from environments with devenv allow More reliable shell activation SecretSpec 0.17 and Cachix integration Near-zero idle CPU usage in the TUI Evaluation cache and automation improvements And many bugfixes! devenv.sh devenv 2.2: attach to running processes and persistent out-of-tree... Fast, Declarative, Reproducible, and Composable Developer Environments using Nix Disclaimer: LLMs have been used 1 post - 1 participant Read full topic ## How GPT-5.6 fuses frontier intelligence with frontier efficiency DevFeed: [How GPT-5.6 fuses frontier intelligence with frontier efficiency]() Original publisher: [Read original article]() Published: 2026-07-29T00:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [Artificial Intelligence](), [Inference](), [Optimization](), [coding](), [ChatGPT](), [codex](), [Claude]() Tags: [agent](), [agentic](), [ai](), [analysis](), [availability](), [benchmarks](), [caching](), [claude](), [codex](), [coding](), [compute](), [cost](), [efficiency](), [engineering](), [gpt](), [inference](), [latency](), [models](), [optimization](), [processes](), [workflows]() ### AI overview GPT-5.6 is presented as a model family designed to balance intelligence and cost. The article describes efficiency improvements across models, inference, and an agentic harness, including load balancing, speculative decoding, caching, kernel optimization, context management, tool usage, and reducing repeated work. ### Source excerpt GPT-5.6 improves AI efficiency across models, inference, and agentic workflows, helping deliver more useful intelligence per dollar. ## Why strict memory overcommit matters for Postgres DevFeed: [Why strict memory overcommit matters for Postgres]() Original publisher: [Read original article]() Author: Kaushik Iska Published: 2026-07-28T00:00:00Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Linux](), [Processes](), [Hardware]() Tags: [clickhouse](), [linux](), [memory](), [postgres](), [processes]() ### AI overview The article explains why ClickHouse Managed Postgres uses strict Linux memory overcommit. Strict accounting turns a potentially instance-wide OOM restart into a single failed query while preserving other connections, with no measurable throughput cost. ### Source excerpt Why ClickHouse Managed Postgres runs strict memory overcommit by default, and how it turns an instance-wide OOM restart into a single failed query -- shown side by side on identical hardware, with no measurable throughput cost. [Next page]()