![[res_cpu.png|64]] When Postgres has a `NULL` wait event, it is actively
working on the CPU. This isn't a bottleneck, but understanding _where_ the
cycles go is key to tuning.
![[TupleProcessing]]
![[MemoryAlgorithms]]
![[ExpressionEvaluation]]
![[Spinning]]