Cancel Running Benchmark

Overview

Flow ID: cancel-benchmark
Category: Performance Benchmarking
Estimated Duration: 10 seconds
User Role: All Users
Complexity: Simple

Purpose: Stop currently running benchmark test suite to free up system resources or terminate if no longer needed.

Trigger

What initiates this flow:

• User manually initiates

Specific trigger: User needs to stop benchmark, typically because:

• Need system resources for other tasks
• Benchmark taking too long
• Want to reconfigure and restart
• Got enough data from partial results

User Intent Analysis

Primary Intent

Immediately stop benchmark testing to free resources or terminate unwanted test run.

Secondary Intents

• Free system resources
• Stop before completion if partial results sufficient
• Correct accidental benchmark start

Step-by-Step Flow

Step 1: Access Benchmarking Page

• User Action: Navigate to Settings > Benchmarking (if not already there)
• System Response: Benchmark page with running test displays

Step 2: Locate Stop Button

• User Action: Find “Stop Benchmark” button
• System Response: Button visible when benchmark running
• UI Elements Visible:
  • “Stop Benchmark” button (prominent)
  • Currently running test highlighted
  • Progress indicator active

Step 3: Click Stop

• User Action: Click “Stop Benchmark”
• System Response:
  • Benchmark stops immediately
  • Running tests marked as “Cancelled”
  • Button changes back to “Run Benchmark”
• UI Elements Visible:
  • Status: “Stopped” or “Cancelled”
  • Partial results visible
  • Tests completed before stop show results
  • Tests not started or cancelled show “Cancelled” status

Final Step: Benchmark Stopped

• Success Indicator:
  • No longer running
  • System resources freed
  • Partial results preserved
• System State Change:
  • Benchmark status: Not running
  • Partial results saved
  • Can be resumed or reset
• Next Possible Actions:
  • Review partial results
  • Resume benchmark (see resume-partial-benchmark.md)
  • Reset and run fresh
  • Use partial data for decisions

Error States & Recovery

QA Note: Simple stop operation with no error conditions. Cancellation always succeeds.

Design Considerations

1. User Trust: Stops reliably and immediately
2. Cognitive Load: Single-click stop

Related Flows

• Run Full Benchmark Suite - What’s being cancelled
• Resume Incomplete Benchmark - Continue after stop

Version History

Notes

Important Considerations:

• Stop is immediate; running test completes then stops
• Partial results preserved
• Can resume from where stopped

Best Practices:

• Stop if system needed urgently
• Review partial results before resetting

Common User Questions:

• “Will I lose results?” - No, completed tests preserved
• “Can I resume?” - Yes, use Continue Benchmark