TYPO3 Core

The TYPO3 DBAL abstraction creates prepared statements for each query for security reasons. Usually that's not a problem but with edge cases it is.
For example when bulk processing entities. Let's say you load 100 entities with one releation to another entity each from the db. The query to fetch the related entity is the same for all 100 entities but 100 prepared statements are created. That's not how prepared statements are supposed to be used. There should be one statement per Query and only the parameters should change. Somewhere inside the DBAL layer all prepared statements seem to be cached, so the RAM usage is growing heavily.

This could be solved by a runtime cache, caching prepared statements for each query and reusing the statements.