Caching - Revision history

Vmurrell at 16:16, 30 October 2025

2025-10-30T16:16:31Z

2025-10-30T15:25:47Z

2025-10-30T15:20:12Z

2023-09-13T12:43:58Z

2023-09-07T08:10:51Z

2023-09-04T14:50:26Z

2022-04-06T10:42:47Z

‎Varnish Cache

2022-04-06T10:42:08Z

‎Cache Purge General

2022-02-16T17:59:37Z

‎Varnish Cache and Security

2021-04-12T21:23:33Z

‎Purging the Cache

@@ Line 1: / Line 1: @@
 [[Category:Fusion Registry Configuration]]
 = Overview =
 <p>The Fusion Registry provides a number of caching solutions to help ensure the performance of both server and client side solutions . The various cache layers include:</p>

← Older revision		Revision as of 15:25, 30 October 2025
Line 1:		Line 1:
−	[[Fusion Registry Configuration]]	+	[[Category:Fusion Registry Configuration]]
		+

	= Overview =		= Overview =

@@ Line 1: / Line 1: @@
-[[Category:Functions]]
+[[Fusion Registry Configuration]]
-[[Category:How_To]]
 = Overview =
 <p>The Fusion Registry provides a number of caching solutions to help ensure the performance of both server and client side solutions . The various cache layers include:</p>

@@ Line 1: / Line 1: @@
 [[Category:Functions]]
 [[Category:How_To]]
 = Overview =
 <p>The Fusion Registry provides a number of caching solutions to help ensure the performance of both server and client side solutions . The various cache layers include:</p>

@@ Line 1: / Line 1: @@
 [[Category:Functions]]
 [[Category:How_To]]
 = Overview =
 <p>The Fusion Registry provides a number of caching solutions to help ensure the performance of both server and client side solutions . The various cache layers include:</p>

@@ Line 10: / Line 10: @@
 = Cache Purge General =
 <p>@see [[Cache_Management_Web_Service#Purge_Cache|Purge Cache Web Service]]</p>
 = HTTP Cache Headers =

@@ Line 9: / Line 9: @@
 = Cache Purge General =
-<p>Regardless of cache types, the Fusion Registry is responsible for purging the cache.</p>
+<p>@see [[Cache_Management_Web_Service#Purge_Cache|Purge Cache Web Service]]</p>
 = Varnish Cache =

@@ Line 52: / Line 52: @@
 == Varnish Cache and Security ==
-f the Fusion Registry has security rules on specific datasets, Varnish Cache will be unaware of this.  Therefore we do not recommend Varnish Cache as a solution for a Fusion Registry which enforces different data access levels.
+If the Fusion Registry has security rules on specific datasets, Varnish Cache will be unaware of this.  Therefore we do not recommend Varnish Cache as a solution for a Fusion Registry which enforces different data access levels.
 == Varnish Cache and Locale ==

@@ Line 104: / Line 104: @@
 == Purging the Cache ==
-The Fusion Cache is automatically deleted on Fusion Registry start-up, so it is not idea as a shared caching solution.   A cache limit is also set, which is configurable, and when the cache reaches 90% of its limit, the Fusion Cache will start purging files.  The order in which the files are purged is based on which file was requested last, meaning cached files that have not been required are the first to go.  Files from the cache are purged in short bursts until the required space is recovered, without bottlenecking the CPU or IO.
+The Fusion Cache is automatically deleted on Fusion Registry start-up, so it is not idea as a shared caching solution.   A cache limit is also set, which is configurable, and when the cache reaches 90% of its limit, the Fusion Cache will start purging files.  The order in which the files are purged is based on which file was requested last, meaning the last accessed cached file will be the first to be deleted.  Files from the cache are purged in short bursts until the required space is recovered, this is to ensure CPU and IO does not become a bottleneck due to a long running purge process.
 == Stale Cache ==