CPU vs IO Bound

Cluster debates whether workloads and applications are primarily CPU-bound or IO-bound, discussing CPU utilization, idling while waiting for IO, context switching overheads, and efficiency in process scheduling.

➡️ Stable 0.6x DevOps & Infrastructure
3,026
Comments
20
Years Active
5
Top Authors
#5907
Topic ID

Activity Over Time

2007
2
2008
13
2009
44
2010
103
2011
75
2012
88
2013
108
2014
101
2015
148
2016
156
2017
184
2018
176
2019
176
2020
225
2021
278
2022
270
2023
297
2024
273
2025
284
2026
27

Keywords

IQ RAM TimeOfMemoryFetchInCycle CPU DOS UUID CyclesSpentDoingInstructions debian.net OS VM cpu bound cpu time io waiting cores server disk slow process

Sample Comments

fooker Nov 25, 2019 View on HN

Because not everything is CPU bound.

leej Feb 5, 2010 View on HN

no they said the opposite that they are surprisingly cpu-bound.

axod Jan 7, 2009 View on HN

They may well be CPU bound because of context switching.

dilyevsky Apr 3, 2023 View on HN

Pretty sure cpu is not a limiting factor here

StreamBright Jun 25, 2019 View on HN

Unless you are doing disk io and most of your CPU cycles spent on it.

xupybd Aug 12, 2022 View on HN

The amount of CPU waste would be negligible.

moeris Dec 23, 2021 View on HN

Most applications are IO bound, not CPU bound. So wasted cycles aren't always that big of a deal.

seba_dos1 Sep 5, 2015 View on HN

Consuming a lot of CPU time and forcing kernel to do that are separate things.

melan13 Apr 24, 2019 View on HN

It does, think twice about the CPU flow.

NuZZ Mar 12, 2013 View on HN

Perhpas he means it's a waste of cpu time :)