Skip to main content

​
Parameter Reference

Quick reference for all available video processing parameters:
ParameterDescription
VIDEO_MAX_CONCURRENTMaximum concurrent video jobs
VIDEO_JOB_RETRY_MAXMaximum retry attempts
VIDEO_JOB_CLEANUP_HOURSJob cleanup time
VIDEO_WORKER_POLL_INTERVAL_MSWorker polling interval

​
Core Parameters

​
VIDEO_MAX_CONCURRENT
integer
Maximum number of video jobs processed simultaneously.Auto-detection:
  • Automatically detected based on available RAM (1 worker per 2GB)
  • Maximum: 16 workers
Examples:
  • 4 - 4 concurrent jobs (default for 8GB RAM)
  • 8 - 8 concurrent jobs (for 16GB RAM)
  • 2 - 2 concurrent jobs (for resource-constrained environments)
  • 16 - Maximum concurrent jobs
If not set, the system auto-detects based on available RAM. Manual configuration overrides auto-detection.
Higher values increase CPU and memory usage. Monitor system resources when adjusting.
​
VIDEO_JOB_RETRY_MAX
integer
default:"3"
Maximum number of retry attempts for failed video jobs.Examples:
  • 3 - Default (3 retry attempts)
  • 5 - More retries for unreliable networks
  • 1 - Single retry for faster failure detection
  • 0 - No retries (not recommended)
Each retry attempts to reprocess the failed video job. Failed jobs are cleaned up after the cleanup period.
​
VIDEO_JOB_CLEANUP_HOURS
integer
default:"24"
Number of hours after which completed or failed jobs are cleaned up from the database.Examples:
  • 24 - Clean up after 1 day (default)
  • 48 - Keep jobs for 2 days
  • 168 - Keep jobs for 1 week
  • 1 - Clean up after 1 hour (aggressive cleanup)
Adjust based on your monitoring needs. Longer retention helps with debugging but increases database size.
​
VIDEO_WORKER_POLL_INTERVAL_MS
integer
default:"1000"
Interval in milliseconds at which the worker polls for new video jobs.Examples:
  • 1000 - Poll every 1 second (default)
  • 500 - Poll every 500ms (faster job pickup)
  • 2000 - Poll every 2 seconds (reduces CPU usage)
  • 5000 - Poll every 5 seconds (lower resource usage)
Lower intervals provide faster job processing but increase CPU usage. Higher intervals reduce CPU but add latency.

​
Configuration Examples

VIDEO_MAX_CONCURRENT=2
VIDEO_JOB_RETRY_MAX=3
VIDEO_JOB_CLEANUP_HOURS=1
VIDEO_WORKER_POLL_INTERVAL_MS=1000
Development configuration with lower concurrency and faster cleanup.

​
Performance Considerations

Concurrency tuning

Balance VIDEO_MAX_CONCURRENT with available CPU cores and RAM. Each worker uses significant resources.

Retry strategy

Set VIDEO_JOB_RETRY_MAX based on network reliability and job criticality.

Cleanup frequency

Adjust VIDEO_JOB_CLEANUP_HOURS to balance database size and debugging needs.

Polling efficiency

Lower VIDEO_WORKER_POLL_INTERVAL_MS for faster processing, higher for reduced CPU usage.
Video processing is resource-intensive. Monitor CPU, memory, and disk I/O when adjusting these parameters. Start with default values and tune based on your specific workload.