title: iBigTable: Number of rows cached per request
body: <p>I'm reading the &quot;Read Performance&quot; subsubsection of subsection 6.3 of <a href="https://www.researchgate.net/profile/Ting_Yu7/publication/261854046_IBigTable_Practical_data_integrity_for_bigtable_in_public_cloud/links/5586fb0208aef58c03a0291a/IBigTable-Practical-data-integrity-for-bigtable-in-public-cloud.pdf" rel="nofollow noreferrer">iBigTable: Practical Data Integrity for BigTable in PublicCloud</a>.
  One of the phrases used is &quot;...number of rows cached per request for a scan.&quot;</p>
  <p>I am new to databases. Is this discussing the idea of a tablet T storing rows (that have recently been used in a query response) in the sense that the next query, q, might result in retrieving some of those cached rows? That is, instead of forwarding q to other tablets, T looks into its cache to see if part of the response to q can be found?</p>
  <p>References for further reading will be much appreciated.</p>