Feature #28902
closed
Configurable ACCESS_TIME precision
0%
Description
Make the precision of $ACCESS_TIME configurable for better query_cache efficiency.
eg. in t3lib/config_default.php:
// default
$TYPO3_CONF_VARS['SYS']['ACCESS_TIME_PRECISION'] = 60;
[...]
$ACCESS_TIME = $EXEC_TIME - ($EXEC_TIME % $TYPO3_CONF_VARS['SYS']['ACCESS_TIME_PRECISION']);
would be nice to see this feature in 4.5 tree.
Updated by Susanne Moog over 13 years ago
Could you explain a bit more about why this would help and where you see the current problems?
Updated by Georg Ringer over 13 years ago
mysql cache doesn't like a new query per secone too much because of enable fields. so with this setting it can cache it for a certain period
Updated by Markus Blaschke over 13 years ago
In our most installations a precision in days would do it - mysql could cache each query for a whole day not only for one minute.
Updated by Susanne Moog over 13 years ago
- Status changed from New to Accepted
- TYPO3 Version changed from 4.5 to 4.7
- Complexity set to easy
Ah, sounds good. As it's a feature it can only go to 4.7 (we already have feature freeze for 4.6) - but maybe the release managers of 4.6 and for 4.5 allow it as a performance fix?
Updated by Oliver Hader over 13 years ago
I guest that ACCESS_TIME is not only used for caching in TYPO3.
Concerning caching I'd prefer to have a new setting/value here - has to be analyzed...
Updated by Oliver Hader over 13 years ago
- Complexity changed from easy to medium
Updated by Ernesto Baschny about 13 years ago
Currently we have (in config_default.php):
$ACCESS_TIME = $EXEC_TIME - ($EXEC_TIME % 60);This is used in the enableFields query, for example, so that those won't generate a new query each second, but keep the same query for the same minute: So that MySQL can use the query-cache and we still having the feature of being able to publish content on a certain minute.
The change was introduced back in 2008 for 4.1:
http://git.typo3.org/TYPO3v4/Core.git?a=commitdiff;h=fd5a82be213c2d779f2383c9469438b1083f7169
Having the precision configurable could be a performance beneficiary option, but will probably only be tuned by very specific sites where the query cache is an issue. It remains proven if tweaking this will really give some real world benefit.
So I would opt for adding this feature in 4.7 and have it proven in the world. It will then be part of the next LTS of course. If it proves so useful by then, we can think about backporting it to 4.5, of course.
Updated by Markus Blaschke over 12 years ago
Is there any progress on this issue?
Updated by Mathias Schreiber almost 10 years ago
- Target version set to 7.2 (Frontend)
Updated by Benni Mack over 9 years ago
- Target version changed from 7.2 (Frontend) to 7.4 (Backend)
Updated by Susanne Moog over 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack about 9 years ago
- Target version changed from 7.5 to 8 LTS
Updated by Markus Mächler over 8 years ago
i would also like to have this feature.
without this, the mysql query cache is useless for TYPO3.
Implementing this would be a big plus!
Updated by Riccardo De Contardi over 7 years ago
- Target version changed from 8 LTS to 9.0
Updated by Susanne Moog almost 7 years ago
- Status changed from Accepted to Closed
As Ernesto stated we currently calculate access time per minute, so the publishing feature will work to the minute but the query cache can still be used during that minute.
Making it configurable to longer times would break the publish feature for little benefit - especially as the query cache is deprecated in new MySQL versions.
Therefor I'd close this ticket for now. If you still see a significant benefit in having this feature feel free to open a new ticket with the corresponding reasoning.