Clarifying dropped iterations definition

Grafana k6 k6-browser
1

Hi, all. I have been trying to do a large load testing by k6 browser. So, I was trying to do that with constant-arrival-rate executor. My goal is to hit the 50k transactions per hour, but I got the result that has too many dropped iterations, it’s about 70 - 80% of all.

However, I was read the document that explains how dropped iterations happen, it’s told me “If this happens later in the test, the dropped iterations might happen because SUT performance is degrading and iterations are taking longer to finish”.

Therefore, I was trying to find the optimal configuration that has dropped iterations 1% below with this configuration

import { browser } from 'k6/browser';
export const options = {
  scenarios: {
    contacts: {
      executor: "constant-arrival-rate",
      rate: 5,
      timeUnit: "1s",
      duration: "5m",
      preAllocatedVUs: 5,
      maxVUs: 10,
      options: {
        browser: {
          type: 'chromium',
        },
      },
    }
  },
  thresholds: {
    checks: ['rate==1.0'],
  },
};

export default async function () {
  const context = await browser.newContext();
  const page = await context.newPage();

  try {
    await page.goto('https://mytest.url);
  } finally {
    await page.close();
  }
}

But it’s still has 10% of dropped iterations, I don’t understand it well because my test succeeds with the using resource of my SUT was too low and had no error, it used only 10% of the CPU and memory was not running out then my test device cpu and ram were not hit 100% at the end.