SShortSingh.
Back to feed

Benchmark: Hostim Leads PostgreSQL Writes, Hetzner Tops Reads vs AWS RDS

0
·1 views

A July 2026 benchmark compared PostgreSQL 16 performance across three platforms — Hostim managed Postgres, AWS RDS db.t4g.medium, and a self-hosted Hetzner CPX22 — all configured with 2 vCPU and 4 GB RAM in a central-Europe region. Hostim recorded the highest write throughput at 2,708 TPS, roughly 2.5 times that of AWS RDS and 2.1 times the default Hetzner setup. Hetzner outperformed the others on read-only workloads due to faster raw per-core CPU speed, while AWS RDS ranked slowest or near-slowest in both write and single-connection commit tests. The write performance gap was attributed largely to network-attached block storage latency on the commit path, which affects both RDS and self-hosted Hetzner. Hostim's €50/month plan includes replication and failover by default, whereas RDS and Hetzner require additional configuration and cost for high availability.

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)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

How Chainlink Proof of Reserve Could Have Flagged TerraUSD's Collapse Early

TerraUSD (UST) collapsed with $18 billion in circulation due to circular collateral backing — UST relied on LUNA, which itself depended on UST demand, with no independent on-chain verification in place. When the peg broke, protocols continued accepting UST as collateral and processing loans against a rapidly depreciating asset because no automated circuit breaker existed. Chainlink's Proof of Reserve (PoR) is designed to address this gap by using a decentralized oracle network to continuously monitor and publish collateral data on-chain, replacing periodic audits with real-time verification. PoR can detect issues such as fractional reserve practices, infinite mint attacks via compromised bridges, and cross-chain collateral opacity that smart contracts cannot natively observe. However, PoR has limits — it verifies what node operators observed from a custodian's system at the time of the last update, meaning it cannot independently confirm the honesty of the custodian's own data reporting.

0
ProgrammingDEV Community ·

Free tool AzureNamer generates CAF-compliant names for 204 Azure resource types

A developer has released AzureNamer, a free browser-based tool that generates Microsoft Cloud Adoption Framework-compliant names for 204 Azure resource types, each enforcing its specific length and character rules. The tool addresses a common pain point where Azure naming constraints vary widely across resource types and are scattered across Microsoft's documentation. Users can export generated names in multiple formats including Terraform, Bicep, JSON, Markdown, and CSV, with parameterized templates that support dev, staging, and production environments. AzureNamer also parses existing resource names back into their components and includes a searchable CAF abbreviations reference. The tool requires no login and runs entirely in the browser, meaning no user input is transmitted externally.

0
ProgrammingDEV Community ·

A11 Architecture Aims to Bridge Gap Between Robot Automation and True Autonomy

A new decision-making framework called A11 proposes a vertical architectural structure for autonomous robots, contrasting with the horizontal module-based pipelines used in current industry systems. Today's robots follow a Perception-to-Behavior-Tree pipeline that executes tasks but cannot represent persistent mission-level intentions or independently resolve conflicts between safety and planning. A11 introduces eleven structured layers — from mission intent and values down to execution and mission evaluation — designed to keep safety constraints immutable and separate from planning algorithms. When a conflict arises, such as a planned route crossing a restricted area, A11 is designed to detect it, log it, generate a revised intention, and continue the mission without human intervention. Proponents argue that without such an architecture, robots remain sophisticated automation tools rather than genuinely autonomous agents capable of explainable, adaptive decision-making.

0
ProgrammingDEV Community ·

Engineer Debugs vLLM PagedAttention KV Cache Corruption That Caused Production Outage

A software engineer responding to an on-call incident discovered that their vLLM-based model serving system had gone down due to KV cache corruption in the PagedAttention layer, with peak request traffic reaching over 14,700 RPS at the time of the alert. Initial debugging attempts — including adjusting timeout settings, restarting Kubernetes pods, and checking GPU health — all failed to resolve the issue, consuming roughly 45 minutes. The root cause ultimately traced back to a single-line fix in the team's Dockerfile. Following the incident, the team added three Grafana-based alerting rules to catch NCCL communication failures and high all-reduce latency before users are impacted in future. The engineer shared the full debugging code and fix on GitHub for others running vLLM with PagedAttention in production environments.