Suggested way of loading users from a csv file across 10 workers

[brtak]

Just wanted to ask if you guys might have a suggested way of loading users from a csv file across 10 containers in a sequence format? Below i've posted an example of the current way we build our config. I've noticed that when we run large loads of around 2000 users in 5 mins across 10 containers we see some users grabbed more often that other users (our CSV file contains over 2000 users). I understand that they are pulled randomly.

I looked at the docs and tried to implement the loadAll config options and also do the loop rules but that seemed to not be supported with running with playwright as I kept getting errors that it could not find the testFunction to use (even though I left that unchanged). So was wondering if you guys might have a good solution to how we could, in theory, load up 10 containers, and somehow allow the containers to go through that file in a sequence order.... but I fear that the containers will not know which users have been previously used from the list.

config:
  target: mywebsite
  phases:
  - arrivalCount: 20
    duration: 2m
    name: Arrival Count Phase 1
  payload:
    path: '../Users/Users.csv'
    fields:
      - 'customerId'
    skipHeader: true
  engines:
    playwright:
      contextOptions:
        viewport:
          width: 1600
          height: 1200
      trace: true
      aggregateByName: true
      extendedMetrics: true
      launchOptions:
        headless: true
  processor: ../tests/checkoutWithAuth.ts
scenarios:
- engine: playwright
  testFunction: checkoutWithAuth
  name: Cart_Checkout_With_Auth
  json:
    customerId: '{{customerId}}'

[hassy]

The best option for this use case is to forego CSVs entirely and use Redis. There's an example here: https://github.com/artilleryio/artillery/tree/main/examples/using-data-from-redis - you can still use CSVs to load data into Redis of course, but the VUs should then load it from Redis to guarantee that VUs only get "fresh" values.

[brtak]

Thanks Hassy!

[brtak]

@hassy or @bernardobridge (since i see previous discussions you've helped similar with). We setup redis accordingly and everything works great locally. When we try to run it in Fargate, we get the following error in our ECS Container. I feel like we're missing something simple but cant seem to find what it is? any ideas?

September 3, 2025 at 11:15 | EXIT | -
-- | -- | --
September 3, 2025 at 11:15 | Error: Failed to compile Typescript processor | -
September 3, 2025 at 11:15 | Build failed with 1 error: | -
September 3, 2025 at 11:15 | Utils/processor.ts:2:22: ERROR: Could not resolve "@upstash/redis" | -
September 3, 2025 at 11:15 | ✘ [ERROR] Could not resolve "@upstash/redis" | -
September 3, 2025 at 11:15 | Utils/processor.ts:2:22: | -
September 3, 2025 at 11:15 | 2 │ import { Redis } from '@upstash/redis'; | -
September 3, 2025 at 11:15 | ╵ ~~~~~~~~~~~~~~~~ | -
September 3, 2025 at 11:15 | You can mark the path "@upstash/redis" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.

package.json dependencies

"dependencies": {
    "artillery": "2.0.24",
    "@upstash/redis": "^1.35.3",
    "dotenv": "^17.2.1",
    "csv-parser": "^3.2.0"
  }

processor.ts

// IMPORTANT: The correct order for Artillery's function parameters is critical!
import { Redis } from '@upstash/redis';
import { checkoutWithAuth } from "../tests/checkoutWithAuth";

const redis = new Redis({
  url: secret,
  token: secret,
});

interface User {
    customerId: string;
}

export async function getUser(): Promise<User> {
    const initialTime = Date.now();

    const res: User | null = await redis.lpop('users');
    console.log('Response from Redis:', res);

    if (res === null) {
        console.error('No users found in Redis');
        throw new Error('err_no_users_found_in_redis');
    }

    const user: User = res;

    const finalTime = Date.now();

    if (process.env.SHOW_TIMING) {
        console.log(`Time taken: ${finalTime - initialTime}ms`);
    }

    console.log('getUser customerId', user);

    return user
}

// The Artillery Playwright engine will call this function
export async function checkoutWithAuthTest(page, context, events, test) {

  const user = await getUser();
  context.vars.customerId = user;
  // Call the actual test function
  return checkoutWithAuth(page, context, events, test);
}

checkoutWithAuth.yml

config:
  target: mysite
  phases:
  - arrivalCount: 10
    duration: 1m
    name: Arrival Count Phase 1
  engines:
    playwright:
      contextOptions:
        viewport:
          width: 1600
          height: 1200
      trace: true
      aggregateByName: true
      extendedMetrics: true
      launchOptions:
        headless: true
  processor: "../Utils/processor.ts"
scenarios:
- engine: playwright
  testFunction: checkoutWithAuthTest
  name: Cart_Checkout_With_Auth

checkoutWithAuth.ts

import { Page } from '@playwright/test';
import { CartLandingPage } from '../POMS/Shop/CartLandingPage';
import { CheckoutPage } from '../POMS/Shop/CheckoutPage';
import { checkoutTestData } from '../Utils/ShopTestData';
import { LoginPage } from '../POMS/SSO/LoginPage';

// Change parameter name from vuContext to context to match
export async function checkoutWithAuth(page: Page, context, events, test) {
  page.setDefaultTimeout(120000);

  const { step } = test;
  

  // Use context instead of vuContext
  const customerId = String(context.vars.customerId);
  console.log(`[checkoutWithAuth] Using customerId: ${customerId}`);

  const cartLandingPage = new CartLandingPage(page);
  const checkoutPage = new CheckoutPage(page);
  const ssoLoginPage = new LoginPage(page);

  await step(login', async () => {
    await ssoLoginPage.get();
    await ssoLoginPage.login(customerId);
  });

  await step('Add_products_to_cart_and_click_checkout', async () => {
    await cartLandingPage.addProductsToCart(true);
  });

  await step('Enter_payment_information', async () => {
    await checkoutPage.enterPaymentInformation(
      checkoutTestData.cardNumber,
      `${checkoutTestData.firstName} ${checkoutTestData.lastName}`,
      checkoutTestData.cvc,
      true
    );
  });

  await step('Click_place_order_and_wait_for_confirmation', async () => {
    await checkoutPage.placeOrder();
  });
}

[brtak]

@hassy thanks. I converted everything to JS and validated that running locally it is working great still. However, we are still getting that same error (see below). We have validated that the package is there on the container we are sending up along with the artillery package as well. We are super confused what we are doing wrong because before we add this package it all works great in Fargate. 😅

Message body: {"event": "workerDone"} | -
-- | --
September 8, 2025, 10:41 | cleanup called, signal: | -
September 8, 2025, 10:41 | EXIT | -
September 8, 2025, 10:41 | worker error, id: 1 Error: Cannot find module '@upstash/redis' | -
September 8, 2025, 10:41 | Require stack: | -
September 8, 2025, 10:41 | - /artillery/test_data/Utils/processor.js | -
September 8, 2025, 10:41 | - /artillery/packages/core/lib/runner.js | -
September 8, 2025, 10:41 | - /artillery/packages/core/index.js | -
September 8, 2025, 10:41 | - /artillery/packages/artillery/lib/artillery-global.js | -
September 8, 2025, 10:41 | - /artillery/packages/artillery/lib/platform/local/worker.js | -
September 8, 2025, 10:41 | at Module._resolveFilename (node:internal/modules/cjs/loader:1365:15) | -
September 8, 2025, 10:41 | at defaultResolveImpl (node:internal/modules/cjs/loader:1021:19) | -
September 8, 2025, 10:41 | at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1026:22) | -
September 8, 2025, 10:41 | at Module._load (node:internal/modules/cjs/loader:1175:37) | -
September 8, 2025, 10:41 | at TracingChannel.traceSync (node:diagnostics_channel:322:14) | -
September 8, 2025, 10:41 | at wrapModuleLoad (node:internal/modules/cjs/loader:235:24) | -
September 8, 2025, 10:41 | at Module.require (node:internal/modules/cjs/loader:1445:12) | -
September 8, 2025, 10:41 | at require (node:internal/modules/helpers:135:16) | -
September 8, 2025, 10:41 | at Object.<anonymous> (/artillery/test_data/Utils/processor.js:2:19) | -
September 8, 2025, 10:41 | at Module._compile (node:internal/modules/cjs/loader:1688:14) { | -
September 8, 2025, 10:41 | code: 'MODULE_NOT_FOUND', | -
September 8, 2025, 10:41 | requireStack: [ | -
September 8, 2025, 10:41 | '/artillery/test_data/Utils/processor.js', | -
September 8, 2025, 10:41 | '/artillery/packages/core/lib/runner.js', | -
September 8, 2025, 10:41 | '/artillery/packages/core/index.js', | -
September 8, 2025, 10:41 | '/artillery/packages/artillery/lib/artillery-global.js', | -
September 8, 2025, 10:41 | '/artillery/packages/artillery/lib/platform/local/worker.js' | -
September 8, 2025, 10:41 | ] | -
September 8, 2025, 10:41 | } | -
September 8, 2025, 10:41 | Artillery Cloud reporting is configured for this test run

// IMPORTANT: The correct order for Artillery's function parameters is critical!
const { Redis } = require('@upstash/redis');
const { checkoutWithAuth } = require("../tests/checkoutWithAuth");

const redis = new Redis({
  url: secret,
  token: secret,
});

async function getUser() {
    const initialTime = Date.now();

    const res = await redis.lpop('users');
    console.log('Response from Redis:', res);

    if (res === null) {
        console.error('No users found in Redis');
        throw new Error('err_no_users_found_in_redis');
    }

    const user = res;

    const finalTime = Date.now();

    if (process.env.SHOW_TIMING) {
        console.log(`Time taken: ${finalTime - initialTime}ms`);
    }

    console.log('getUser customerId', user);

    return user;
}

// The Artillery Playwright engine will call this function
async function checkoutWithAuthTest(page, context, events, test) {
  const user = await getUser();
  context.vars.customerId = user;
  // Call the actual test function
  return checkoutWithAuth(page, context, events, test);
}

module.exports = {
  getUser,
  checkoutWithAuthTest
};

[brtak]

Just an update, we tried to manually copy the files into the artillery directory where things get accessed but still got the same error. Wondering if there is some fargate issue present here with having packages outside of just "artillery"?

[hassy]

@brtak what does the table that lists autodetected dependencies when you run a test with run-fargate look like? Possibly an issue with that - the error message suggests that @upstash/redis cannot be found.

[brtak]

@hassy here is what is logged. For additional context, if we remove that package and remove the reference to it in processor, the run starts just fine. If we add the package and then reference it in processor like in the above examples it throws that error. :

Region:      us-west-1
build	09-Sep-2025 14:31:19	  Count:       1
build	09-Sep-2025 14:31:19	  Cluster:     artilleryio-cluster
build	09-Sep-2025 14:31:19	  Launch type: ecs:fargate (On-demand)
build	09-Sep-2025 14:31:19	
build	09-Sep-2025 14:31:20	Preparing test bundle... [20:31:20]
build	09-Sep-2025 14:31:20	Test bundle prepared... [20:31:20]
build	09-Sep-2025 14:31:20	Test bundle contents:
build	09-Sep-2025 14:31:20	┌──────────────────────────────┬──────┬───────┐
build	09-Sep-2025 14:31:20	│ Name                         │ Type │ Notes │
build	09-Sep-2025 14:31:20	├──────────────────────────────┼──────┼───────┤
build	09-Sep-2025 14:31:20	│ configs/checkoutWithAuth.yml │ file │       │
build	09-Sep-2025 14:31:20	├──────────────────────────────┼──────┤       │
build	09-Sep-2025 14:31:20	│ Utils/processor.js           │ file │       │
build	09-Sep-2025 14:31:20	├──────────────────────────────┼──────┤       │
build	09-Sep-2025 14:31:20	│ POMS/Shop/CartLandingPage.js │ file │       │
build	09-Sep-2025 14:31:20	├──────────────────────────────┼──────┤       │
build	09-Sep-2025 14:31:20	│ POMS/Shop/CheckoutPage.js    │ file │       │
build	09-Sep-2025 14:31:20	├──────────────────────────────┼──────┤       │
build	09-Sep-2025 14:31:20	│ Utils/ShopTestData.js        │ file │       │
build	09-Sep-2025 14:31:20	├──────────────────────────────┼──────┤       │
build	09-Sep-2025 14:31:20	│ Constants/Constants.js       │ file │       │
build	09-Sep-2025 14:31:20	├──────────────────────────────┼──────┤       │
build	09-Sep-2025 14:31:20	│ POMS/SSO/LoginPage.js        │ file │       │
build	09-Sep-2025 14:31:20	├──────────────────────────────┼──────┤       │
build	09-Sep-2025 14:31:20	│ tests/checkoutWithAuth.js    │ file │       │
build	09-Sep-2025 14:31:20	└──────────────────────────────┴──────┴───────┘
build	09-Sep-2025 14:31:20	

[hassy]

thanks! this looks like an issue with automatic detection of dependencies. Artillery should have detected that @upstash/redis is being used and included it in the bundle. What you could try is generate an empty package.json, add @upstash/redis to it and then pass it to run-fargate explicitly with --packages flag, e.g.:

artillery run-fargate mytest.yml --packages ./path/to/package.json