Bug #24285
closed
Caching Framework in Option "File-Backend" reaches Folder-Limit of OS
Added by Florian Bachmann almost 14 years ago.
Updated over 13 years ago.
Description
The caching Framework generates one subfolder for each page in TYPO3, in typo3temp/cache/tags/.... (pageId_xxxxx)
The limit of allowed subfolders is 32000 in EXT2/EXT3, or 64000 in NTFS/Reiser
the subfolders should be hierarchicaly ordered.
So on websites with more than 32.000 Pages the Website crashes - see attached screenshots
(issue imported from #M16670)
Files
- ext2 / ext3 do have a limit of 32k subfolders (ext4: unlimited)
- The fileBackend was redone with 4.4 and up: It doesn't store the tags in a separate file structure anymore, but in the data file itself. This makes get() and set() very fast, but flushByTag() is scales insanely bad (hint: do not use the filebackend in 4.4 and up for content caches!)
- 4.4 and up do not separate to different folders anymore, btree handling in ext3 should be able to get() and set() files pretty quick even if there are tons of files in a directory
We will not change the basic handling in 4.3 anymore as it was already redone with 4.4 and up, I doubt that we will hit filesystem bounds with the new handling.
Thus I tend to close this issue with "won't fix" unless someone comes up with a good reason not to do so. If the handling still needs to be changed for whatever reason in 4.4 and up, we could tackle it in another issue and we must patch to FLOW3 first to be able to backport to TYPO3 version 4.
- Status changed from Needs Feedback to Rejected
- Target version deleted (
0)
This is not relevant in younger TYPO3 versions anymore and will not be fixed in 4.3.
Also available in: Atom
PDF
Updated by 