TYPO3 Core

Many functions, including, but not limited to:

• typolink() and it's variants
• getPage() and variants
• getRootline(), which could benefit SQL rewrite to avoid SELECTs in a while loop.

does repetitive, identical queries to DB's page table.
For my current project, within one page render, it's frequent to see the exact same query being issued to the database 3-12 times.

My biggest concern is when, for one page render, the total number of SELECT's sent for the page table exceed the number of row available in the table.

All the code using the page table would greatly benefit some caching.
Since pages are the central unit of Typo3, a central repository for retrieving ems could allow full caching of the table and save hundreds of calls to the database for a single page request.
It also could use the current caching backend to free up the database for content that's volatile from request-to-request.