4
4
Cache
5
5
=====
6
6
7
- Using cache is a great way of making your application run quicker. The Symfony cache
8
- component is shipped with many adapters to different storages. Every adapter is
7
+ Using a cache is a great way of making your application run quicker. The Symfony cache
8
+ component ships with many adapters to different storages. Every adapter is
9
9
developed for high performance.
10
10
11
11
The following example shows a typical usage of the cache::
@@ -27,7 +27,7 @@ The following example shows a typical usage of the cache::
27
27
// ... and to remove the cache key
28
28
$pool->delete('my_cache_key');
29
29
30
- Symfony supports the Cache Contracts, PSR-6/16 and Doctrine Cache interfaces.
30
+ Symfony supports Cache Contracts, PSR-6/16 and Doctrine Cache interfaces.
31
31
You can read more about these at the :doc: `component documentation </components/cache >`.
32
32
33
33
.. _cache-configuration-with-frameworkbundle :
42
42
This is a service that you will interact with. Each pool will always have
43
43
its own namespace and cache items. There is never a conflict between pools.
44
44
**Adapter **
45
- An adapter is a *template * that you use to create Pools .
45
+ An adapter is a *template * that you use to create pools .
46
46
**Provider **
47
- A provider is a service that some adapters are using to connect to the storage.
47
+ A provider is a service that some adapters use to connect to the storage.
48
48
Redis and Memcached are example of such adapters. If a DSN is used as the
49
49
provider then a service is automatically created.
50
50
@@ -104,7 +104,7 @@ The Cache component comes with a series of adapters pre-configured:
104
104
* :doc: `cache.adapter.redis </components/cache/adapters/redis_adapter >`
105
105
106
106
Some of these adapters could be configured via shortcuts. Using these shortcuts
107
- will create pool with service id of ``cache.[type] ``
107
+ will create pools with service IDs that follow the pattern ``cache.[type] ``.
108
108
109
109
.. configuration-block ::
110
110
@@ -298,13 +298,13 @@ You can also create more customized pools:
298
298
],
299
299
]);
300
300
301
- Each pool manages a set of independent cache keys: keys of different pools
301
+ Each pool manages a set of independent cache keys: keys from different pools
302
302
*never * collide, even if they share the same backend. This is achieved by prefixing
303
303
keys with a namespace that's generated by hashing the name of the pool, the name
304
304
of the compiled container class and a :ref: `configurable seed<reference-cache-prefix-seed> `
305
305
that defaults to the project directory.
306
306
307
- Each custom pool becomes a service where the service id is the name of the pool
307
+ Each custom pool becomes a service whose service ID is the name of the pool
308
308
(e.g. ``custom_thing.cache ``). An autowiring alias is also created for each pool
309
309
using the camel case version of its name - e.g. ``custom_thing.cache `` can be
310
310
injected automatically by naming the argument ``$customThingCache `` and type-hinting it
@@ -330,7 +330,7 @@ Custom Provider Options
330
330
331
331
Some providers have specific options that can be configured. The
332
332
:doc: `RedisAdapter </components/cache/adapters/redis_adapter >` allows you to
333
- create providers with option ``timeout ``, ``retry_interval ``. etc. To use these
333
+ create providers with the options ``timeout ``, ``retry_interval ``. etc. To use these
334
334
options with non-default values you need to create your own ``\Redis `` provider
335
335
and use that when configuring the pool.
336
336
@@ -422,7 +422,7 @@ item in a cache chain, Symfony stores it in all pools sequentially. When
422
422
retrieving an item, Symfony tries to get it from the first pool. If it's not
423
423
found, it tries the next pools until the item is found or an exception is thrown.
424
424
Because of this behavior, it's recommended to define the adapters in the chain
425
- in order from the fastest to the slowest.
425
+ in order from fastest to slowest.
426
426
427
427
If an error happens when storing an item in a pool, Symfony stores it in the
428
428
other pools and no exception is thrown. Later, when the item is retrieved,
@@ -486,9 +486,9 @@ Using Cache Tags
486
486
----------------
487
487
488
488
In applications with many cache keys it could be useful to organize the data stored
489
- to be able to invalidate the cache more efficient . One way to achieve that is to
489
+ to be able to invalidate the cache more efficiently . One way to achieve that is to
490
490
use cache tags. One or more tags could be added to the cache item. All items with
491
- the same key could be invalidate with one function call::
491
+ the same key could be invalidated with one function call::
492
492
493
493
use Symfony\Contracts\Cache\ItemInterface;
494
494
use Symfony\Contracts\Cache\TagAwareCacheInterface;
@@ -636,14 +636,14 @@ Clearing the Cache
636
636
637
637
To clear the cache you can use the ``bin/console cache:pool:clear [pool] `` command.
638
638
That will remove all the entries from your storage and you will have to recalculate
639
- all values. You can also group your pools into "cache clearers". There are 3 cache
639
+ all the values. You can also group your pools into "cache clearers". There are 3 cache
640
640
clearers by default:
641
641
642
642
* ``cache.global_clearer ``
643
643
* ``cache.system_clearer ``
644
644
* ``cache.app_clearer ``
645
645
646
- The global clearer clears all the cache in every pool. The system cache clearer
646
+ The global clearer clears all the cache items in every pool. The system cache clearer
647
647
is used in the ``bin/console cache:clear `` command. The app clearer is the default
648
648
clearer.
649
649
0 commit comments