Project

General

Profile

Actions

Feature #16105

closed

Setting a max limit for chached things in filesystem or database

Added by Andreas Balzer over 18 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Install Tool
Target version:
-
Start date:
2006-04-29
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Hi! It would be nice, if it's possible to say TYPO3 should only cache things until it reaches XXX MB and then deletes the oldest files automaticly. Would be good for hosted webspaces where you only have e.g. 20 MB database size but TYPO3 saves 60 MB in it..

(issue imported from #M3380)

Actions #1

Updated by Martin Kutschker over 18 years ago

An automated thingy will probably be too complicated, but I can image an item in Tool>DBcheck.

Actions #2

Updated by Wouter Wolters over 11 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • PHP Version deleted (4)

Hosting is improved alot, is this still an FEATURE that is needed?

Actions #3

Updated by Philipp Gampe over 11 years ago

This does not make sense IMHO. If you drop caches so early, then you lose the benefit of caching. People should GC the cache tables more often than or even write an own GC task.

Actions #4

Updated by Christian Kuhn about 11 years ago

  • Status changed from Needs Feedback to Closed

Yeah. I'm also not in favor of such a feature. This however may be possible with an own cache backend ... if anyone still wants that, it could be implemented in an extension and if it turns out to be useful it may be added to the core with a new issue.

Actions

Also available in: Atom PDF