Batch Processing Statistics

From Grooper Wiki
Revision as of 17:00, 16 May 2025 by Dgreenwood (talk | contribs) (Created page with "Grooper logs a variety of processing statistics for production Batches. These stats can be seen when selecting a Batch's "Statistics" tab in the Batches Page or when returning query results from the Stats Page. Stats are logged for each step in the Batch's Batch Process, according to its Activity. Some of theses stats are obvious by their name. Some of them are less so. This article seeks to document the different Batch processing statistics for each Activity in Grooper...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Grooper logs a variety of processing statistics for production Batches. These stats can be seen when selecting a Batch's "Statistics" tab in the Batches Page or when returning query results from the Stats Page. Stats are logged for each step in the Batch's Batch Process, according to its Activity. Some of theses stats are obvious by their name. Some of them are less so.

This article seeks to document the different Batch processing statistics for each Activity in Grooper. This will help you better understand the stats Grooper collects and create the kinds of queries you want in the Stats page.

Review Stats

Stats collected independent of Review Viewers used

Scan Viewer Stats

Data Viewer Stats

Classification Viewer Stats

Thumbnail Viewer Stats

Folder Viewer Stats

Code Activity Stats

Stats collected independent of Activity type

Regardless of the Activity the Batch Process Step is running, every step will record the following stats:

  • Tasks Processed - This is the total number of tasks in the Batch Process Step that are successfully processed.
    • Note if the task errors out, it will not be recorded.
      • If there are 100 available tasks and they all complete successfully, 100 tasks are recorded.
      • If there are 100 available tasks and 10 of them error out, 90 tasks are recorded.
    • This is determined by how many tasks are available in scope.
      • If the step is scoped to the Batch level (and the step completes successfully), there will be a single task recorded.
      • If the step is scoped to the Folder level and there are 10 Batch Folders (and they all complete successfully in the step), there will be 10 tasks recorded.
      • If the step is scoped to the Page level and there are 100 Batch Pages (and they all complete successfully in the step), there will be 100 tasks recorded.
  • Execution Time - This is the total time elapsed it takes the Batch Process Step to run from start to finish or "total elapsed time".
  • Processing Time - This is how much time each machine thread spends processing tasks added together.
    • This is not to be confused with "Execution Time".
    • Example: An Activity Processing service uses 10 threads to process tasks.
      • There are 10 Batch Folders in a Batch at Folder level 1.
      • The Extract step is scoped to Folder level 1. So, there are 10 available tasks to process.
      • All threads pick up the 10 Extract tasks at roughly the same time.
      • The Extract step's "Execution Time" would be roughly 10 seconds.
        • It would take roughly 10 seconds to run the Extract step from start to finish.
        • 10 tasks running concurrently @ 10 seconds per thread = A total elapsed time of 10 seconds.
      • The Extract step's "Processing Time" would be 100 seconds (or 1m 40s)
        • Each thread in the Batch Process takes 10 seconds to process a single Extract task. With 10 total tasks, that's a total of 100 seconds.
        • 10 tasks @ 10 seconds per thread = 100 total seconds (each thread's processing time added together)