<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>InnoDB on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/innodb/</link><description>Recent content in InnoDB on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 22 Apr 2024 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/innodb/index.xml" rel="self" type="application/rss+xml"/><item><title>Databases (4): Storage Engines — How Data Hits Disk</title><link>https://www.chenk.top/en/databases/04-storage-engines/</link><pubDate>Mon, 22 Apr 2024 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/databases/04-storage-engines/</guid><description>&lt;p>Every SQL statement you write eventually becomes bytes written to a disk. The component responsible for this translation — the storage engine — determines your database&amp;rsquo;s performance characteristics more than almost any other factor. Two tables with identical schemas and identical data can perform wildly differently depending on the storage engine underneath. Understanding this layer explains &lt;em>why&lt;/em> databases behave the way they do.&lt;/p>
&lt;hr>
&lt;h2 id="the-basics-pages-extents-and-tablespaces" class="heading-anchor">The Basics: Pages, Extents, and Tablespaces&lt;a href="#the-basics-pages-extents-and-tablespaces" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;p>Databases do not read or write individual rows from disk. Disk I/O operates on &lt;strong>pages&lt;/strong> (also called blocks), typically 4 KB, 8 KB, or 16 KB.&lt;/p></description></item></channel></rss>