Configuring Queue and Thread Settings in WebReports

Queue and Thread settings control how many report operations WebReports can run simultaneously and how many requests can wait for processing.

Increasing these values may improve throughput when sufficient resources are available. However, it may also increase processor usage, memory usage, and database contention.

Accessing Queue and Thread settings

1. Sign in to WebReports with an administrator account.
2. Select Configuration from the navigation menu.
3. Select Settings.
4. Select Queue and Threads.

Understanding threads and capacity

Threads and capacity control different parts of report processing:

Increasing capacity allows more requests to wait, but it does not increase the number of reports that can run simultaneously.

For example, if Scheduled Reports Parallel Threads is set to 2, WebReports can run two scheduled reports simultaneously. Additional scheduled reports wait until a thread becomes available.

Scheduled Reports Parallel Threads

Scheduled Reports Parallel Threads determines the maximum number of scheduled reports that can run simultaneously.

Additional scheduled reports wait until a thread becomes available.

Default: 1 thread

Increasing this value allows WebReports to process more scheduled reports concurrently but may increase demand on the application server and reporting databases.

Scheduled Reports Capacity

Scheduled Reports Capacity determines how many scheduled report requests can wait for execution.

When the queue reaches capacity, additional scheduled requests may be delayed until space becomes available.

Default: 50 requests

Note: Capacity controls waiting requests. It does not control how many scheduled reports run simultaneously.

Server Administration Capacity

Server Administration Capacity determines the maximum queued workload available for background server-administration operations.

This setting prevents an unbounded background queue from affecting the application.

Default: 500 operations

Important: Confirm changes to this setting with BridgeWorks Support before adjusting the default value.

Queue and Download Reports Parallel Threads

Queue and Download Reports Parallel Threads determines how many Queue and Download report requests can run simultaneously.

Additional requests wait until a thread becomes available.

Default: 5 threads

Increasing this value may allow more requests to run concurrently, but it may also increase server and database utilization.

Queue and Download Reports Capacity

Queue and Download Reports Capacity determines how many Queue and Download report requests can wait for execution.

Higher values allow WebReports to accept more requests during busy periods.

Default: 50 requests

Note: Increasing capacity does not increase the number of reports that run simultaneously.

Changing Queue and Thread settings

Before changing these settings:

• Review current processor, memory, and database utilization.
• Determine whether delays are caused by limited processing capacity or report performance.
• Change one setting at a time when possible.
• Test significant changes outside normal production hours.
• Monitor application and database performance after making a change.
• Document the original and updated values.

Changes apply immediately to the current application instance and within approximately 60 seconds on other instances.

Important: Increasing thread counts does not always improve performance. Excessive concurrency can increase server load, database contention, and overall report-processing time.

When to review these settings

Consider reviewing Queue and Thread settings when:

• Scheduled reports are consistently waiting for execution.
• Users experience delays when queuing or downloading reports.
• Many report requests are submitted simultaneously.
• Application and database resources remain consistently underutilized while requests are waiting.
• The number of users or scheduled reports has increased significantly.

Queue delays can also be caused by complex reports, slow database queries, limited database resources, or network performance. Review those factors before increasing concurrency.

Related articles

• Configuring Application Settings in WebReports
• Queueing Reports in WebReports
• Downloading Reports in WebReports
• Schedule Overview