Maeris logo
Get started for free

Running Performance Tests

Learn how to execute performance tests in Maeris, monitor test execution in real-time, and manage running tests.

Overview

Running a performance test involves executing your configured test, monitoring its progress in real-time, and managing the test execution. Maeris provides tools to help you track test progress and make adjustments as needed.

Starting a Performance Test

  1. Select Your Test: Choose the performance test you want to run
  2. Review Configuration: Verify test settings, load profile, and thresholds

    Make sure all settings are correct before starting

  3. Check Prerequisites: Ensure your API is accessible and test environment is ready
  4. Start Test: Click "Run Test" or "Start Test" button
  5. Monitor Progress: Watch real-time metrics and test progress

Real-Time Monitoring

During test execution, Maeris provides real-time monitoring of key metrics and test progress.

Live Metrics

  • Virtual Users: Current number of active virtual users
  • Requests per Second: Real-time throughput
  • Response Times: Live response time percentiles (P50, P95, P99)
  • Error Rate: Current error percentage
  • Success Rate: Percentage of successful requests
  • Test Progress: Time elapsed and remaining

Live Charts and Visualizations

Real-time charts help you visualize test performance as it happens.

Available Charts

  • Response Time Chart: Shows response times over time
  • Throughput Chart: Displays requests per second
  • Error Rate Chart: Shows error rates over time
  • Virtual Users Chart: Displays active virtual users
  • Percentile Chart: Shows P50, P95, P99 response times

Managing Running Tests

You can manage running tests by pausing, stopping, or adjusting them during execution.

Test Controls

  • Pause: Temporarily pause test execution (can be resumed)
  • Stop: Stop test execution (cannot be resumed)
  • Adjust Load: Increase or decrease virtual users during test (if supported)
  • View Details: Access detailed metrics and logs during execution

Test Execution States

Common States

  • Queued: Test is waiting to start
  • Initializing: Test is being set up
  • Running: Test is actively executing
  • Paused: Test execution is paused
  • Completed: Test finished successfully
  • Stopped: Test was stopped manually
  • Failed: Test encountered an error

Monitoring Best Practices

  • Watch Key Metrics: Monitor response times, error rates, and throughput
  • Check for Anomalies: Look for unexpected spikes or drops in metrics
  • Monitor System Resources: Watch server CPU, memory, and network if available
  • Track Thresholds: Monitor if performance thresholds are being met
  • Take Notes: Document any observations during test execution
  • Be Ready to Stop: Have a plan to stop tests if they're causing issues

Troubleshooting During Execution

If you notice issues during test execution, here are common problems and solutions.

Common Issues

  • High Error Rates: Check API availability, reduce load, or check for rate limiting
  • Slow Response Times: Monitor server resources, check for bottlenecks
  • Connection Errors: Verify network connectivity and API availability
  • Test Timeout: Check test duration settings and API response times
  • Resource Exhaustion: Reduce load or check server capacity

Test Completion

When a test completes, you'll have access to comprehensive results and analysis.

Post-Test Actions

  • Review test results and summary
  • Analyze performance metrics
  • Check if thresholds were met
  • Export results for reporting
  • Compare with previous test runs
  • Share results with team members

Best Practices

  • Monitor Actively: Watch test execution, especially during ramp-up
  • Start During Off-Peak: Run tests during off-peak hours when possible
  • Have a Stop Plan: Know when and how to stop tests if needed
  • Document Observations: Note any issues or anomalies during execution
  • Don't Interrupt Unnecessarily: Let tests complete unless there's a critical issue
  • Review Results Promptly: Analyze results soon after test completion
  • Share Findings: Communicate important findings to your team

Next Steps