Add general cache seeding and configuration information

Author: nikolajlauridsen

15/umbraco-cms/extending/creating-custom-seed-key-provider.md

@@ -1,5 +1,5 @@
 ---
-description: A guid to creating a custom seed key provider for Umbraco
+description: A guide to creating a custom seed key provider for Umbraco
 ---
 
 # Creating a Custom Seed Key Provider

15/umbraco-cms/reference/cache/cache-seeding.md

@@ -0,0 +1,42 @@
+---
+description: Information about cache seeding
+---
+
+# Cache Seeding
+
+From version 15 and onwards Umbraco uses a lazy loaded cache, this means content is loaded into the cache on an as-needed basis
+I.E. whenever a piece of content is shown on the website for the first time it first needs to be loaded into the cache.
+
+Loading the content into the cache causes a delay. This delay is dependent on the latency between your server and your database, but is generally minimal.
+However, for certain pages, for instance the front page, you may not want this delay to be there, the role of cache seeding is to solve this issue.
+
+## How it works
+
+Cache seeding is based upon the concept of a `ISeedKeyProvider`, the role of the seed key provider, is to specify what keys needs to be seeded.
+There's two types of seed key providers, a `IDocumentSeedKeyProvider` which specifies which document should be seeded, and a `IMediaSeedKeyProvider` which specifies which media should be seeded.
+
+During startup all the `ISeedKeyProviders` are run, and the keys they return are seeded into their respective caches, `IPublishedContentCache` for documents, and `IPublishedMediaCache` for media.
+Additionally whenever a document or media is then later changed, the cache will be updated with the changed content immediately, ensuring the content is always present in the case.
+However, here it's important to note, that this means that whenever a piece of content is changed, Umbraco needs to go through the seeded keys to see if it's a piece of seeded content that was updated.
+Because of the need the check all seeded keys, Umbraco caches the keys themselves during startup. This means that if you have a dynamic seed key provider, any newly added content won't be considered seeded until the server restarts,
+for instance when seeding by document type any new content using the specified document type won't be seeded until a server restart.
+
+## Seed key providers
+
+### Default implementations.
+
+By default, umbraco ships with two seed key providers for documents, and a single one for media.
+
+For documents there is the `ContentTypeSeedKeyProvider` this seeds all documents of the given document types specified through app settings.
+
+For both documents and media there is the `BreadthFirstKeyProvider` this provider does a breadth first traversal of the content and media tree respectively, seeding N number of content specified in the app settings.
+
+Configuration for the default seed key providers can be found in the [cache settings section.](../configuration/cache-settings.md)
+
+### Custom seed key providers
+
+It's also possible to implement your own seed key providers, these are run alongside the default seed key providers on startup.
+The returned keys are of all the seed key providers are unioned into a single set, this means that there will be no duplicates, so you don't need to worry consider this.
+However, as mentioned above the provided keys are cached, meaning that only the keys returned at startup will be considered seeded until the server restarts and the provider is run again.
+
+For a specific example of how to implement a custom seed key provider, see [Creating a Custom Seed Key Provider](../extending/creating-custom-seed-key-provider.md).

15/umbraco-cms/reference/configuration/cache-settings.md

@@ -0,0 +1,151 @@
+---
+description: Information on the Cache settings section
+---
+
+# Cache settings
+
+## Seeding settings
+
+The seeding settings allows you to specify which content should be seeded into your cache, for more information on cache seeding see [Cache Seeding.](../cache/cache-seeding.md)
+
+### ContentTypeKeys
+
+The `ContentTypeKeys` setting is used to specify which document types should be seeded into the cache. The setting is a comma-separated list of document type keys.
+
+```json
+"Umbraco": {
+  "CMS": {
+    "Cache": {
+      "ContentTypeKeys": ["e811405e-0190-4d3e-8387-7558521eec81", "419e89fb-8cff-4549-a074-9f8a30687828", "e0d71146-8205-4cf4-8236-f982b392259f"],
+    }
+  }
+}
+```
+
+### DocumentBreadthFirstSeedCount
+
+The `DocumentBreadthFirstSeedCount` setting is used to specify how many documents should be seeded into the cache when doing a breadth first traversal, the default value is 100.
+
+
+```json
+"Umbraco": {
+  "CMS": {
+    "Cache": {
+      "DocumentBreadthFirstSeedCount": 500
+    }
+  }
+}
+```
+
+## MediaBreadthFirstSeedCount
+
+The `MediaBreadthFirstSeedCount` setting is used to specify how many media items should be seeded into the cache when doing a breadth first traversal, the default value is 100.
+
+```json
+"Umbraco": {
+  "CMS": {
+    "Cache": {
+      "MediaBreadthFirstSeedCount": 500
+    }
+  }
+}
+```
+
+## Cache entry settings
+
+The entry settings allows you to specify how long cache entries should be kept in the cache, the cache entry settings are identical for documents and media.
+
+## LocalCacheDuration
+
+Specifies the duration that cache entries should be kept in the local memory cache, the default value is 24 hours.
+
+```json
+"Umbraco": {
+  "CMS": {
+    "Cache": {
+      "Entry": {
+        "Document": {
+          "LocalCacheDuration": "2.00:00:00"
+        },
+        "Media": {
+          "LocalCacheDuration": "50.00:00:00"
+        }
+      }
+    }
+  }
+}
+```
+
+## RemoteCacheDuration
+
+Specifies the duration that cache entries should be kept in the remote cache, second level cache, this setting is only relevant if second level cache is configured. The default value is 1 year.
+
+```json
+"Umbraco": {
+  "CMS": {
+    "Cache": {
+      "Entry": {
+        "Document": {
+          "RemoteCacheDuration": "100.00:00:00"
+        },
+        "Media": {
+          "RemoteCacheDuration": "150.00:00:00"
+        }
+      }
+    }
+  }
+}
+```
+
+## SeedCacheDuration
+
+Specifies the duration that seeded cache entries should be kept in the cache. The default value is 1 year.
+
+```json
+"Umbraco": {
+  "CMS": {
+    "Cache": {
+      "Entry": {
+        "Document": {
+          "SeedCacheDuration": "200.00:00:00"
+        },
+        "Media": {
+          "SeedCacheDuration": "250.00:00:00"
+        }
+      }
+    }
+  }
+}
+```
+
+# NuCache Settings
+
+For backwards compatibility reasons, certain settings are still located under the `Umbraco:CMS:NuCache` settings node.
+
+## UsePagedSqlQuery
+
+Setting `UsePagedSqlQuery` to `False`  your project will use the `Fetch` method instead of the `QueryPaged` method when rebuilding the NuCache files. This will increase performance on bigger Umbraco websites with a lot of content when rebuilding the NuCache.
+
+```json
+"Umbraco": {
+  "CMS": {
+    "NuCache": {
+      "UsePagedSqlQuery": false
+    }
+   }
+ }
+
+```
+## SqlPageSize
+
+Specifying the `SqlPageSize` will change the size of the paged sql queries, by default the value is 1000.
+
+```json
+"Umbraco": {
+  "CMS": {
+    "NuCache": {
+      "SqlPageSize": 500
+    }
+   }
+ }
+```