mirror of
https://github.com/silverstripe/silverstripe-framework
synced 2024-10-22 14:05:37 +02:00
DOCS Filesystem capacity issue potential on caches
Context: https://github.com/silverstripe/silverstripe-framework/issues/6678
This commit is contained in:
parent
d76dd257e4
commit
40d19d04ec
@ -137,6 +137,17 @@ Depending on your hosting and deployment mechanisms,
|
|||||||
you may need to configure the plugin to copy files instead.
|
you may need to configure the plugin to copy files instead.
|
||||||
See [silverstripe/vendor-plugin](https://github.com/silverstripe/vendor-plugin) for details.
|
See [silverstripe/vendor-plugin](https://github.com/silverstripe/vendor-plugin) for details.
|
||||||
|
|
||||||
|
### Caches
|
||||||
|
|
||||||
|
Silverstripe relies on various [caches](https://docs.silverstripe.org/en/4/developer_guides/performance/caching/)
|
||||||
|
to achieve performant responses. By default, those caches are stored in a temporary filesystem folder,
|
||||||
|
and are not shared between multiple server instances. Alternative cache backends such as Redis can be
|
||||||
|
[configured](https://docs.silverstripe.org/en/4/developer_guides/performance/caching/).
|
||||||
|
|
||||||
|
While cache objects can expire, when using filesystem caching the files are not actively pruned.
|
||||||
|
For long-lived server instances, this can become a capacity issue over time - see
|
||||||
|
[workaround](https://github.com/silverstripe/silverstripe-framework/issues/6678).
|
||||||
|
|
||||||
### Error pages
|
### Error pages
|
||||||
|
|
||||||
The default installation includes [silverstripe/errorpage](https://addons.silverstripe.org/add-ons/silverstripe/errorpage),
|
The default installation includes [silverstripe/errorpage](https://addons.silverstripe.org/add-ons/silverstripe/errorpage),
|
||||||
|
@ -25,6 +25,11 @@ executing the action is limited to the following cases when performed via a web
|
|||||||
* A user is logged in with ADMIN permissions
|
* A user is logged in with ADMIN permissions
|
||||||
* An error occurs during startup
|
* An error occurs during startup
|
||||||
|
|
||||||
|
Caution: Not all caches are cleared through `flush=1`.
|
||||||
|
While cache objects can expire, when using filesystem caching the files are not actively pruned.
|
||||||
|
For long-lived server instances, this can become a capacity issue over time - see
|
||||||
|
[workaround](https://github.com/silverstripe/silverstripe-framework/issues/6678).
|
||||||
|
|
||||||
## Configuration
|
## Configuration
|
||||||
|
|
||||||
We are using the [PSR-16](http://www.php-fig.org/psr/psr-16/) standard ("SimpleCache")
|
We are using the [PSR-16](http://www.php-fig.org/psr/psr-16/) standard ("SimpleCache")
|
||||||
|
Loading…
Reference in New Issue
Block a user