Advanced Configuration

Configure Pebble Flow to meet your processing needs.

Depending on the computational complexity of your spreadsheets, you may need to change your server's default configuration settings.

Environment VariableDefault ValueCommentsServer Type
CALLBACK_MAX_RETRY_COUNT5The maximum number of times the server will attempt a requested service callback.worker
JOBS_IDLE_TIME10000The time in milliseconds the server will wait before checking for a job when the jobs queue is empty.worker
REQUESTS_IDLE_TIME10000The time in milliseconds the server will wait before checking for a request when the requests queue is empty.worker
SCENARIOS_IDLE_TIME10000The time in milliseconds the server will wait before checking for a scenario when the scenarios queue is empty.worker
PEBBLE_CACHE_SIZE32The number of pebbles stored in the pebble cache. Pebbles already loaded in memory are initialized faster by the server. Note that each server node has a separate pebble cache. If your library of Pebbles exceeds this number by a factor of 5, it may make sense to increase this value. Consider the size of your Pebble Flow Server nodes when changing this value.worker
RUNNER_PROCESSOR_RATIO1.5This ratio is multiplied by the number of core processors to obtain the size of the thread pool that runs pebbles. For instance if there are four cores and this value is set to 1.5, the thread pool size will be 6 (1.5 x 4). Consider the thread-to-memory ratio when setting this value. Lower this value If your computations are memory-intensive. Increase this value is your computations are small in size but you have many of them to complete.worker
DATA_CACHE_SIZE256The number of data files stored in memory when executing a workflow. Once loaded, data files can be reused. This is useful for speeding up group-level calculations, where a single data file may contain multiple groups. Care should be used when setting this value, as it is not possible to estimate data file sizes accurately. Consider the size of your Pebble Flow Server nodes and the characteristics of your workflows when changing this value.worker
PROCESSING_WAITING_TIME1000The duration the server will wait, in milliseconds, before checking on the status of a set of running pebbles' completion. Setting this value to a smaller number increases the frequency of completion checks.worker
REQUEST_TIMEOUT_IN_SECONDS600Pebble Flow no longer leases messages. Messages are deleted as soon as they are pulled from the queue.
The time the server will lease a message in seconds from the job and request queues. Do not set this value higher than 86400 (24 hours). This parameter will be deprecated in upcoming releases.
DEPRECATED
STORAGE_PASSWORD-Set when configuring for deployment.
WORKFLOW_TIMEOUT_DURATION_IN_SECONDS43200The time in seconds the server will allow a workflow to complete without aborting the execution.orchestrator
JOBS_IDLE_TIME250The time in milliseconds the server will wait to check for more messages when the orchestrator queue is empty.orchestrator

Benign Environment Variables

These configuration parameters are NOT to be changed.

Environment VariableDefault ValueComments
ADMIN_EMAIL-Set when configuring for deployment. Not used after deployment.
ADMIN_FIRST_NAME-Set when configuring for deployment. Not used after deployment.
ADMIN_LAST_NAME-Set when configuring for deployment. Not used after deployment.
API_KEY-Set when configuring for deployment. DO NOT CHANGE.
AZURE_MANAGED_APP_RESOURCE_ID-Set during deployment. DO NOT CHANGE
ENVPRODSet when configuring for deployment. DO NOT CHANGE.
ORGANIZATION_NAME-Set when configuring for deployment. DO NOT CHANGE.
PENDING_JOBS_LIMIT20Deprecated. No longer used.
PENDING_REQUESTS_LIMIT100000Deprecated. No longer used.
PENDING_SCENARIOS_LIMIT5Deprecated. No longer used.
PERSIST_MESSAGEStrueDeprecated. No longer used.
PORT8080Set when configuring for deployment. DO NOT CHANGE.
WEBSITE_RUN_FROM_PACKAGE-Set when configuring for deployment. DO NOT CHANGE.