Filesystem Cache AdapterEdit this page
Warning: You are browsing the documentation for Symfony 5.3, which is no longer maintained.
Read the updated version of this page for Symfony 6.1 (the current stable version).
This adapter offers improved application performance for those who cannot install tools like APCu or Redis in their environment. It stores the cache item expiration and content as regular files in a collection of directories on a locally mounted filesystem.
The FilesystemAdapter can optionally be provided a namespace, default cache lifetime, and cache root path as constructor parameters:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
use Symfony\Component\Cache\Adapter\FilesystemAdapter; $cache = new FilesystemAdapter( // a string used as the subdirectory of the root cache directory, where cache // items will be stored $namespace = '', // the default lifetime (in seconds) for cache items that do not define their // own lifetime, with a value 0 causing items to be stored indefinitely (i.e. // until the files are deleted) $defaultLifetime = 0, // the main cache directory (the application needs read-write permissions on it) // if none is specified, a directory is created inside the system temporary directory $directory = null );
The overhead of filesystem IO often makes this adapter one of the slower choices. If throughput is paramount, the in-memory adapters (Apcu, Memcached, and Redis) or the database adapters (PDO) are recommended.
In order to use tag-based invalidation, you can wrap your adapter in TagAwareAdapter, but it's often more interesting to use the dedicated FilesystemTagAwareAdapter. Since tag invalidation logic is implemented using links on filesystem, this adapter offers better read performance when using tag-based invalidation:
1 2 3
use Symfony\Component\Cache\Adapter\FilesystemTagAwareAdapter; $cache = new FilesystemTagAwareAdapter();