Documentation | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Configuring the Cache > Partitioning the cache
Partitioning the cache
Help | Content Gateway | v8.5.x
You can manage your cache space more efficiently and restrict disk usage by creating cache partitions of different sizes for specific protocols. You can further configure these partitions to store data from specific origin servers and domains. See Partitioning the cache according to origin server or domain.
 
* 
Important 
The partition configuration must be the same on all nodes in a cluster.
HTTP is the only protocol supported.
Making changes to partition sizes and protocols
After you have configured your cache partitions based on protocol, you can make changes to the configuration at any time. Before making changes, note the following:
*
You must stop Content Gateway before you change the cache partition size and protocol assignment.
*
When you increase the size of a partition, the contents of the partition are not deleted. However, when you reduce the size of a partition, the contents of the partition are deleted.
*
When you change the partition number, the partition is deleted and then re-created, even if the size and protocol type remain the same.
*
When you add new disks to your Content Gateway node, the partition sizes specified in percentages increase proportionately.
*
A lot of changes to the partition sizes might result in disk fragmentation, which affects performance and hit rate. It is recommended that you clear the cache (see Clearing the cache) before making many changes to cache partition sizes.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Configuring the Cache > Partitioning the cache
Copyright 2023 Forcepoint. All rights reserved.