Skip to main content

Understanding Queue and Thread Settings in WebReports

Garrick Guillory
Updated

Article Goal

Learn how Queue and Thread settings control report execution, scheduling capacity, and system performance within WebReports.

What are Queue and Thread Settings?

Queue and Thread settings determine how many reports WebReports can process simultaneously and how many requests can wait for processing.

These settings help administrators balance report performance, server resources, and user demand.

Increasing these values allows more reports to be processed concurrently but may also increase CPU, memory, and database utilization.

Accessing Queue and Thread Settings

  1. Sign in to WebReports with an account that has administrative permissions.
  2. Select Management from the navigation menu.
  3. Click Configuration.
  4. Locate the Queue and Threads section.

Queue and Thread Settings

Scheduled Reports Parallel Threads

Specifies the maximum number of scheduled reports that can execute simultaneously.

For example, if this value is set to 2, two scheduled reports can run at the same time. Any additional scheduled reports will wait until a thread becomes available.

Scheduled Reports Capacity

Specifies the maximum number of scheduled report requests that can be queued for execution.

When the capacity limit is reached, additional scheduled reports may be delayed until space becomes available in the queue.

Queue & Download Reports Parallel Threads

Specifies the maximum number of Queue and Download report requests that can execute simultaneously.

This setting affects reports executed through the Queue and Download options within WebReports.

Queue & Download Reports Capacity

Specifies the maximum number of Queue and Download report requests that can be waiting for execution.

Higher values allow more report requests to be accepted during periods of heavy usage.

Server Administration Capacity

Specifies the maximum number of administrative operations that can be processed simultaneously.

This setting helps control the workload associated with administrative tasks performed within WebReports.

Understanding Threads vs Capacity

Threads

Threads determine how many reports can actively run at the same time.

Example:

Scheduled Reports Parallel Threads = 2

Report A = Running
Report B = Running
Report C = Waiting
Report D = Waiting

When one report completes, the next report in the queue begins processing.

Capacity

Capacity determines how many requests can wait in line for processing.

Example:

Queue & Download Reports Capacity = 50

Up to 50 report requests can be waiting for execution at any given time.

Best Practices

Small Environments

  • Scheduled Reports Parallel Threads: 1–2
  • Queue & Download Parallel Threads: 2–5

Medium Environments

  • Scheduled Reports Parallel Threads: 2–4
  • Queue & Download Parallel Threads: 5–10

Large Environments

Adjust these settings based on:

  • Available CPU resources
  • Available memory
  • Database performance
  • Number of concurrent users
  • Average report complexity

Important: Increasing thread counts does not always improve performance. Excessive thread counts may increase server load, database contention, and overall processing times.

When Should These Settings Be Changed?

Consider adjusting Queue and Thread settings when:

  • Scheduled reports are backing up.
  • Users experience delays running reports.
  • Large numbers of reports are being executed simultaneously.
  • Server resources are consistently underutilized.
  • Additional report processing capacity is required.

Changes should be tested during non-production hours whenever possible.

Related Articles

 

Related articles

Comments

0 comments

Please sign in to leave a comment.