Oriel — AI & technology worth noticing, every day.

Codex Was Torching Your SSD and Nobody Noticed for Months

Post · https://dev.to/varshithvhegde/codex-was-torching-your-ssd-and-nobody-noticed-for-months-4c5h

Your Codex log file looked fine. Your SSD counters did not. The file was small. That was...

First seen by Oriel on .

AI summary

The article reports that Codex CLI’s TRACE logging caused roughly 37 TB of writes in 21 days on one machine, while version 0.142.0 reportedly reduced logging activity by about 85%.

  • The logs_2.sqlite database stayed small because new entries were retained while older rows were deleted, masking substantial cumulative storage activity.
  • TRACE entries reportedly comprised 70.7% of retained log-body size, including WebSocket, OpenTelemetry, dependency-bridge, and client transport messages.
  • SQLite WAL checkpoints, deletes, indexes, and SSD-level write amplification can turn frequent small log events into significantly more physical writes.
  • The investigation says RUST_LOG=warn did not fully suppress the relevant logging sink, reducing confidence in the expected logging override.
  • The 37 TB measurement came from one heavy user, while the 85% reduction after 0.142.0 was an early result rather than a universal guarantee.

#codex cli #sqlite #ssd endurance #rust logging

Generated by gpt-5.6-sol. Check the original for details.

Metric trends

Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained

Reactions

Total public reactions reported by the source; distinct from points and likes.

  • DEV Community: 48, latest observation ; +33 over observed period since

Comments

Comment count reported by the source.

  • DEV Community: 42, latest observation ; +28 over observed period since

Aliases

SourceExternal IDURL
DEV Community4961856https://dev.to/varshithvhegde/codex-was-torching-your-ssd-and-nobody-noticed-for-months-4c5h Read discussion