Task #56979
Epic #55070: Workpackages
Epic #55065: WP: Overall System Performance (Backend and Frontend)
Epic #55656: Optimize overall Extbase performance
Story #55168: Optimize Extbase generic persistence
Add setting for DataMapper to enable preparedStatements
| Status: | New | Start date: | 2014-03-17 | |
|---|---|---|---|---|
| Priority: | Could have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | Extbase | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 6.2 | Complexity: | ||
| PHP Version: | Sprint Focus: |
Description
A big improvement for preparedStatements could be get when there would be a setting in the DataMapper:fetchRelated() (getPreparedQuery) to enable preparedStatements for fetching the relations because the queries would mostly be the same and only differ in the uid.
Related issues
History
#1 Updated by Xavier Perseguers over 1 year ago
From the implementation of prepared statement I've seen, I have the feeling the prepared statement is recreated for each execution. If I'm correct, and to get most out of it, it should really be reused instead.
#2 Updated by Marc Bastian Heinrichs over 1 year ago
Xavier Perseguers wrote:
From the implementation of prepared statement I've seen, I have the feeling the prepared statement is recreated for each execution. If I'm correct, and to get most out of it, it should really be reused instead.
Oh, yes, I think you are right. At the moment there is absolutely no improvement, if it is enabled in the query settings. The query object will be recreated every time instead of reusing an already created one.
Felix this is not fixed in the query cache patch, is it?
#3 Updated by Felix Oertel over 1 year ago
Urgs ... might be true, not sure. ;) Will try to catch Xavier and have a look at it.
#4 Updated by Helmut Hummel about 1 year ago
Felix Oertel wrote:
Urgs ... might be true, not sure. ;) Will try to catch Xavier and have a look at it.
What is the status on this one?