week 5 journal index

 

Indexes are designed to speed up queries by allowing the database to quickly locate rows without scanning the entire table. However, as the author explains, there are situations where an index lookup can still be slow, even though an index is being used.

The term slow index doesn’t mean the index is broken or “degenerated.” Instead, it refers to the extra work the database must do after the initial tree traversal. Once the database finds the right index entries, it may need to follow the leaf node chain to locate all matching values, and then fetch the corresponding table rows, which are often scattered across many blocks. These additional steps can require many reads from disk, slowing down performance.

In short, a “slow index” happens not because the index is damaged, but because retrieving the actual data involves extra I/O operations. The author emphasizes that rebuilding indexes doesn’t fix this—real performance issues come from how data is accessed and distributed, not from the index structure itself.

Comments

Popular posts from this blog

Week 2 Learning Journal 5 Parts

Week 4 Journal

BOOK REPORT EXTRA CREDIT