Urgent.News

What's breaking now, across thousands of outlets.

Tech

Fast Disks, Slow WAL Sync: Finding Linux Writeback Throttling

As described in the previous post , the primary now uses a high-I/O Ultra disk. Reads and writes took fractions of a millisecond, yet PostgreSQL WAL synchronization averaged 25-30 ms. Removing synchronous-standby waits didn't help: synchronous_commit=local still requires local WAL durability. With device-read constraints reduced and remote acknowledgments excluded, I traced the primary's…

The primary database server utilizes an ultra high-I/O disk, with PostgreSQL write-ahead log (WAL) synchronization taking an average of 25-30 milliseconds. Despite disabling synchronous standby waits, the WAL synchronization time remained the same. By tracing the synchronization call across the guest-OS boundary, it was discovered that Linux writeback throttling was causing the delay.

The relevant PostgreSQL counters show a mean WAL sync time of 24.995 milliseconds. The writeback throttling (WBT) can cause a process to sleep before the work reaches the device, affecting the overall synchronization time. Even with a healthy latency controller, the admission waits in WBT can lead to slow synchronization. The findings suggest that provisioning more disk IOPS does not change the guest-OS admission rule, but rather focuses on the caller's progress through writeback.

In this setup, HorizonDB delegates durable WAL handling and data page persistence to dedicated storage services, avoiding the Linux throttling issue and achieving higher throughput compared to this PostgreSQL configuration.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Handle Empty Vector Search Results: Fresh Lexical and Web Recovery

The page says duplicate_detection_gap : to handle empty vector search results, the help center should fall back instead of accepting a record with no evidence.

  • System implements fallback methods for empty vector search results
  • Semantic search finds near-duplicates, rejects low-evaluation candidates
  • Keyword retrieval prioritizes recent information, web search as last resort

Cloud CI Email Tests Need an AWS Boundary

Email verification tests often fail for reasons that have nothing to do with the application. A shared inbox is slow, an old message is read by the wrong test, or a CI retry consumes a token that the…

  • Email verification tests fail due to slow inboxes, wrong message recipients, or CI token reuse.
  • Proposed AWS boundary separates control, delivery, and evidence for test emails.
  • Fixture identity and run ID are given to CI job; fixture expires with job completion.

Idempotent publishing jobs #546o0

Every job gets an id and a state machine: queued, running, retry, published. Deduplicate by job id before writing a publication record. Related Source repository Mbin instance Author profile on DEV

Vibe directing: letting a sentence edit a video timeline without trampling your hand edits

Disclosure up front: we build ClickPop, an AI video studio, and this post is about a design problem we hit while building its editor.

  • Vibe directing allows editing videos by specifying changes in text, not altering rendered shots.
  • Timeline is the source of truth; agent communicates in editor actions, not its own language.
  • Preserve hand-edited layers; agent reads diffs to plan edits around manual changes.

More from Tuesday 17 November →