Codex SQLite feedback logs can write ~640 TB/year, risking rapid SSD endurance consumption
By
1996fanrui
Summary
Codex (likely GitHub Copilot's CLI agent) has a bug where its SQLite feedback log database continuously writes massive amounts of data to the user's SSD. After 21 days of uptime, one user observed 37 TB written, extrapolating to ~640 TB/year. This could consume a typical consumer SSD's full warranted write endurance (e.g., 600 TBW) in under a year, potentially causing premature drive failure.
Source
Hacker NewsCodex SQLite feedback logs can write ~640 TB/year, risking rapid SSD endurance consumptiongithub.comKey quotes
· 4 pulledCodex is continuously writing a large amount of data to the local SQLite feedback log database
On my machine, after about 21 days of uptime, the main SSD has written about 37 TB.
That extrapolates to roughly 640 TB/year. On a 1 TB SSD, that is about 640 full-drive writes per year.
Some consumer SSDs are rated around 600 TBW, so this could consume roughly a full drive's warranted write endurance in less than a year.
You might also wanna read
16-year-old SATA II SSD survives 1 petabyte of writes, exceeding its endurance rating by 25x
An enthusiast conducted an experiment writing 1 petabyte of data to a 16-year-old Sandisk P4 SATA II SSD, which survived 25 times its rated
tomshardware.com·14d ago16-year-old SATA II SSD survives 1 petabyte of writes, exceeding its endurance rating by 25x
An enthusiast conducted an experiment writing 1 petabyte of data to a 16-year-old Sandisk P4 SATA II SSD, which survived 25 times its rated
tomshardware.com·14d agoDurable Objects, Workers - Billing for SQLite Storage
Durable Objects, Workers - SQLite in Durable Objects GA with 10GB storage per object
Log Explorer - Extended retention
Typhon Database: Three Configurable Durability Modes in a Single WAL for Flexible Workloads
This article is part of a series about building a database engine called Typhon in C#. It discusses how Typhon implements three different du
dev.to·1mo ago
Comments
Sign in to join the conversation.
No comments yet. Be the first.