diff options
| author | Michael Cahill <michael.cahill@wiredtiger.com> | 2012-11-16 15:17:09 +1100 |
|---|---|---|
| committer | Michael Cahill <michael.cahill@wiredtiger.com> | 2012-11-16 15:17:09 +1100 |
| commit | 6375da7e522aea5180c7459d14011f27e40ac397 (patch) | |
| tree | f425be3f521571bc187e1d0b962374e9573c0012 | |
| parent | cbd566ddf4101d0d30268c9953367505d6e6fe09 (diff) | |
| download | mongo-6375da7e522aea5180c7459d14011f27e40ac397.tar.gz | |
s_whitespace
| -rw-r--r-- | src/docs/cache-configuration.dox | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/docs/cache-configuration.dox b/src/docs/cache-configuration.dox index 276de80e74e..0faf0eaf144 100644 --- a/src/docs/cache-configuration.dox +++ b/src/docs/cache-configuration.dox @@ -22,7 +22,7 @@ and the granularity at which the cache pool is redistributed among connections - called the chunk size. The shared cache implementation assigns a certain amount of cache to each -participating database. Each database manages its allocated cache +participating database. Each database manages its allocated cache as it would when not using a shared cache - thus databases using a shared cache can have different eviction policies. There is a thread that monitors the cache usage of each database and redistributes the cache among @@ -30,7 +30,7 @@ participants according to where it is most likely to improve performance. The cache is redistributed in chunks which are of a configurable size. Once a database has had a chunk of cache added or removed it will be given time to start effectively using that cache before it is considered for further -adjustment. If a small chunk size is configured it will take longer for the +adjustment. If a small chunk size is configured it will take longer for the shared cache to adjust to changes in participants. Reallocation of resources happens periodically and whenever a database joins the shared cache. |