Write Policies: Write-Through vs Write-Back Traffic, Dirty Blocks and the Final Flush
This lesson is part of the course
In this lesson
You count the bytes that travel to memory on a short read/write trace under write-through and under write-back, including dirty evictions and the final flush, and see which policy saves traffic.
Buy the course once for $9.99 to unlock every lesson and lab, the final exam and the certificate – lifetime access, no subscription.
Lessons in this course
- The Memory Hierarchy: Sizes, Latencies, Cycles to Time and Why Locality Matters Locked
- Address Bits: Offset, Index and Tag from Cache Size, Block Size and Ways Locked
- A Direct-Mapped Cache on a Trace: Last Use of a Set, Stored Tag, Hit or Miss Locked
- Hit Rate and Miss Types: Compulsory vs Conflict Misses and the Best You Could Reach Locked
- 2-Way Set-Associative with LRU: Two Ways per Set, Last-Use Times and the Victim Locked
- Average Memory Access Time: Hit Time, Miss Rate, Miss Penalty and a Second Level Locked
- Write Policies: Write-Through vs Write-Back Traffic, Dirty Blocks and the Final Flush Locked
- Comparing Cache Designs: Size × Block Size, Miss Penalty, AMAT per Design and a Chart Locked