Feature #16733
closed
Set a db size limit then clear cache
0%
Description
It would be nice to have an option, where an admin can config a DB size limit. As soon as this limit is reached, T3 should immediatly clear all caches. It's an important feature wish, because a server can completly 'crash', if the whole harddrive or db is full, because of too big cache tables. Example: Imagine a search robot sees your calendar and requests each day, starting from 1.1.1970. If every page is cached, the server has a real problem. E.g.: Vservers become completly freezed and won't react on any connection request. Even the shutdown command doesn't work then. So it would be nice to have an option to say: "If there are only 20 MB left: Clear all caches!"
(issue imported from #M4550)
Updated by Michael Stucki almost 18 years ago
What about using the "pageCacheToExternalFiles" feature? It can be found in the Install Tool of 4.0.
Updated by Andreas Balzer almost 18 years ago
This does not solve the problem. T3 is just writing every single bit in can write to the harddrive.. There has to be a 'do something when limit is reached' option.
Updated by Oliver Hader almost 18 years ago
For the example with the calendar it would probably better to use cHash, to only store days, that really exist in your database. So if a search-engine tries to spider 1970-01-01 - what might not be in your calendar - no correct cHash exists and nothing is cached.
But I like the idea of a global $TYPO3_CONF_VARS['SYS']['maxCacheSize'], that limits the cache size to a maximum. Not everyone has a own webserver, but a webhosting package with e.g. 100 MB of database space. Any browser, like firefox behaves similar for caching fetched web data - you can set a limit. But it has to be defined, what should happend if that maximum is reached:
a) Clear all cache
b) Clear the oldest cache data and behave like a "cache stack"
Possibly a better place for discussion on that issue is the dev-list on lists.netfielders.de?
Updated by Andreas Balzer almost 18 years ago
Hi Oliver!
Well i don't think that the mailinglists and newsservers would be a good place to discuss this, as it would never reach the core of T3.. I have tried discussions in the list (with different topics) many times, but I almost don't get an answer there..
To your question about how T3 should react I'm going to give my standard answer.. ;) The admin should be able to decide somewhere.. Maybe in install tool?
It would be really great if something like this can be integrated into T3 4.1
Updated by Alexander Opitz over 11 years ago
- Status changed from New to Needs Feedback
- Target version deleted (
0) - PHP Version deleted (
4)
As this report is very old, is the handling in newer TYPO3 CMS Versions (like 6.0/6.1) more like you expect it?
Updated by Alexander Opitz about 11 years ago
- Status changed from Needs Feedback to Closed
No feedback for over 90 days.