All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Examining the Claim That I/O Is No Longer the Bottleneck in Programming Tasks

By

benhoyt

4mo ago· 7 min readenInsight

Summary

The article examines the claim that I/O is no longer the bottleneck in programming tasks like word frequency counting, challenging the common belief that I/O is the limiting factor. It references Ben Hoyt's blog post which argues that sequential read speeds have improved dramatically while CPU speeds have stagnated, making I/O less of a bottleneck than previously thought. The author tests this claim by measuring sequential read speeds (1.6 GB/s on cold cache, 12.8 GB/s on warm cache) and questions whether word frequency counting can actually achieve these speeds on a single thread, suggesting that CPU processing might now be the limiting factor rather than I/O.

Key quotes

· 3 pulled
Sequential read speed has come a long way, while CPU speed has stagnated.
I'm getting 1.6 GB/s sequential reads on a cold cache, and 12.8 GB/s on a warm cache (best of five).
But it should be possible to count word frequencies at a speed of 1.6 GB/s even on a single thread, right?
Snippet from the RSS feed
Nov 27th, 2022

You might also wanna read