Expression queues

Server or workspace administrators can maintain and configure workspaces on the Expression Queue State and Statistics page. The page provides important information related to expressions issues. You can use this page to ensure that the server is not affected for certain expression configurations.
Note: To view the expression queue, you must either be a global administrator, or have the global permission Business Rules.
To get the best understanding of the expressions information, look at all the data and consider other factors, such as server restarts. The page shows an account of status and is updated automatically every minute. Because resources are required to calculate and update the status and statistics, after you view this page, navigate away from the page to save resources.
Important: The statistics on this page begin to be measured at the date and time at the top of the page. The date and time are considered in all numbers on this page.

Expression queue status and statistics

Table 1. Expression queue status and statistics
Field Description
Current Queue State
  • Queued Expressions: Number of expressions in the queue that are waiting to be run
  • Running Expressions: Number of expressions in the queue that are started but not completed
  • Concurrent Expression Threads: Number of threads on all nodes that are running the expressions
Expression Queue History Graph
  • Queued: Number of queued expressions over time. This number is displayed as a line in the graph.
  • Running: Number of running expressions over time. This number is displayed as a line in the graph.
  • Added: Number of expressions that are added to the queue. This number is displayed as a bar in the graph.
  • Successful: Number of expressions that ran. This number is displayed as a bar in the graph.
  • Failed: Number of expressions that ran with errors. This number is displayed as a bar in the graph. A message with details about the error is displayed in the expression holder attribute.
Select the graph horizon by clicking the All (displays all history since dawn), 24 hours, 1 hour, 5 minutes, or 1 minute links.
Queue Throughput
  • Successful Evaluations: Number of expressions that ran
  • Failed Evaluations: Number of expressions that ran with errors
  • Number of Added or Changed Expressions: The sum of all the new and changed expressions.
Queue Efficiency The lower the numbers are for queue efficiency, the fewer expression container attributes have the Pending Update message.
  • Successful Evaluation Mean Time: The mean time for running an expression
  • Average Latency: The average time an expression is in the queue before a thread starts to run the expression, regardless of whether errors occurred
  • Max Latency: The maximum time an expression is in the queue before a thread starts to run the expression, regardless of whether errors occurred
  • Average Queue Time: The average time to add, run, and complete an expression, regardless of whether errors occurred
  • Max Queue Time: The maximum time to add, run, and complete an expression, regardless of whether errors occurred
Top 5 Slowest Expressions The names and configurations of the five expressions in the application that run the slowest
Note: These statistics are not available when you use the Oracle database.
Top 5 Slowest Expressions on Specific Attributes The names and configurations of the five expressions that run the slowest in certain elements
Note: These statistics are not available when you use the Oracle database.

Feedback