Do you need to cluster GeoWebCache for high availability?
GeoWebCache is quite an efficient piece of software, as such it normally does not need clustering for performance reasons (GeoWebCache running on an old notebook with a seeded tile can literally flood a gigabit line), but it may still make sense to cluster GeoWebCache for high availability reasons.
What kind of files does GeoWebCache open?
GeoWebCache will probably open lots of files from the file system the cache is stored on, depending on the request load, though through short periods of time, as it opens the tile files to deliver their contents to the client.
How much memory do I need for GeoWebCache?
If not possible, use a Java 5 JRE. JREs other than those released by Sun may work correctly, but are not tested nor supported. GeoWebCache does not need a lot of heap memory assigned to the JVM. Usually 512M is just fine if its the only web application running on the servlet container.
What kind of JRE do I need for GeoWebCache?
GeoWebCache speed depends in part on the chosen Java Runtime Environment (JRE). For best performance use a Java 6 JRE. If not possible, use a Java 5 JRE. JREs other than those released by Sun may work correctly, but are not tested nor supported. GeoWebCache does not need a lot of heap memory assigned to the JVM.
What happens when a quota is reached in GeoWebCache?
When a disk quota is reached, further tiles will be saved at the expense of other tiles which will be truncated. The Least Frequently Used (LFU) policy will analyze the disk quota page store and delete the pages of tiles that have been accessed the least often.
How are disk quotas managed in GeoWebCache 1.15.2?
Disk quotas are managed by the gwc-diskquota- .jar library, which uses an embedded Berkeley DB Java Edition database in a directory called diskquota_page_store. This directory is created under the cache directory, next to the meta-store database directory, and is used to store tile usage statistics as well as to record cache disk usage.