Skip to content

Commit a7713a7

Browse files
fix-1429 - Updated documentation
1 parent abcb38f commit a7713a7

File tree

1 file changed

+27
-0
lines changed
  • documentation/en/user/source/production

1 file changed

+27
-0
lines changed

documentation/en/user/source/production/index.rst

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,33 @@ Resource Allocation
102102

103103
Also see https://github.com/GeoWebCache/geowebcache/wiki/Estimating-the-number-of-tiles-and-size-on-disk for table that can be used to estimate how much storage you need and how long seeding will take
104104

105+
Seeder thread pool configuration
106+
++++++++++++++++++++++++++++++
107+
108+
The number of concurrent seed tasks that GeoWebCache can execute is controlled by an internal
109+
thread pool. You can configure its sizes using environment variables (values shown are
110+
defaults used when variables are not set):
111+
112+
- ``GWC_SEEDER_CORE_POOL_SIZE``: core pool size, defaults to ``16``
113+
- ``GWC_SEEDER_MAX_POOL_SIZE``: maximum pool size, defaults to ``32``
114+
115+
Example (Linux/macOS):
116+
117+
.. code-block:: bash
118+
119+
export GWC_SEEDER_CORE_POOL_SIZE=8
120+
export GWC_SEEDER_MAX_POOL_SIZE=16
121+
# start your servlet container / GeoWebCache here
122+
123+
On Windows (PowerShell):
124+
125+
.. code-block:: powershell
126+
127+
$Env:GWC_SEEDER_CORE_POOL_SIZE = "8"
128+
$Env:GWC_SEEDER_MAX_POOL_SIZE = "16"
129+
# start your servlet container / GeoWebCache here
130+
131+
These settings control the pool used to run seed tasks.
105132

106133
Clustering
107134
----------

0 commit comments

Comments
 (0)