NonBlockingLoadTest.java

WebClient client = WebClient.builder()
      .baseUrl("http://" + args[0])
      .build();

Flux
  .generate(AtomicLong::new, (state, sink) -> {
    long i = state.getAndIncrement();
    sink.next(i);
    return state;
  })
  .limitRate(1)
  .flatMap(n -> client.get().uri("/MYENDPOINT").exchange())
  .doOnNext(resp -> {
    if (resp.statusCode().is2xxSuccessful())
      counter.increment();
  })
  .blockLast();

@DarrenForsythe I like to think you don't need to make one and only one monitoring system choice inside an org, especially if you can convince those around you to stand up an OSS product for limited use like this while still using the expensive vendor option for production cases for as long as that is justifiable.

Hi, you may be interested in https://gatling.io/ instead of JMeter for a more complete product than a simple main program

Disclaimer: Gatling author here

Hi,

• indeed, Gatling uses a non blocking architecture, not a one-thread-per-virtual-user one + blocking IO.
• what you're doing is only realistic wrt server to server traffic where you share one global connection pool and SSLContext. If you want to simulate web traffic realistically, each virtual user must have its own connections and SSLSessions.

Regards