Skip to main content
AIDevOps
  • Learn
  • Learning Paths
  • Practice
  • Open Source
  • Books
  • Engineering

    AI DevOpsThe full map of building and operating AI servicesLLMOpsLLM deployment ¡ evaluation ¡ observabilityHands-on ProjectsBuild AI Agent projects

    Knowledge

    DocsTechnical documentationBlogEngineering articlesPloggerDevelopment log feed

    Validate

    Certification3-level skills certification ¡ coming soon
AI Models
LlamaTutorial|MistralTutorial|GemmaTutorial|DeepSeekTutorial|QwenTutorial
đŸ§Ē Testing
k6JMeternGrinder
🤖 AI Applied Development
Applied AI Intro & RoadmapHugging FaceLangChainLlamaIndexLLMOps|LangGraphMCPMulti-AgentAgent Evaluation
🧠 AI Core
AI Intro & RoadmapML FundamentalsLLM Fundamentals|Python AIC++|PyTorchTensorFlowJAX
🧠 AI Agent Development
Finance AI AgentLLM API ServerStock Investing AgentAIOps AI AgentEducation AI AgentCoding AI Agent
🌱 Spring Cloud
Spring Intro & RoadmapSpring Cloud GatewaySpring BootJava|Spring AISpring SecuritySpring BatchSpring JPA
đŸŗ DevOps
DevOps Intro & RoadmapLinuxDockerCI/CD|Kubernetes BasicsK8s AdvancedPrometheusGrafana
🧱 Infrastructure
Infrastructure Intro & RoadmapNginxRedis
â˜ī¸ Cloud
Cloud Intro & RoadmapAWSGCPAzureNCPCloudflare
🎨 Frontend
Frontend Intro & RoadmapJavaScriptTypeScript|ReactNext.js|VueNuxt|Electron
📱 Mobile
Mobile Intro & RoadmapKotlinAndroidFlutter
âš™ī¸ Backend
Backend Intro & RoadmapPython BasicsFastAPIDjangoFlask|CGoGinNode.js
💾 Database
DB Intro & RoadmapCore SQLOracleMySQLPostgreSQL|MongoDBVector DB
AIDevOps

Engineering AI. From Code to Production.
An engineering learning platform for building and operating AI and AI Agents

Learn

  • All Guides
  • Learning Paths
  • AI Tutorial
  • Practice
  • Books

Resources

  • AI DevOps
  • LLMOps
  • Hands-on Projects
  • Docs
  • Blog
  • Plogger
  • Open Source
  • Certification (coming soon)

Start Here

  • AI Core Roadmap
  • AI Applied Development Roadmap
  • Spring Cloud Roadmap
  • DevOps Roadmap
  • Infrastructure Roadmap

 

  • Cloud Roadmap
  • Frontend Roadmap
  • Mobile Roadmap
  • Backend Roadmap
  • Database Roadmap
Š 2026 AIDevOps. All rights reserved.
Terms of ServicePrivacy PolicySitemaptestforge.kr
Load Testing Guide

🌐 nGrinder Complete Guide

Visitors

nGrinder is an open-source distributed load testing platform developed by Naver. It manages the Controller and Agents through a web UI and makes complex scenarios easy to build with Groovy/Jython scripts.

← Back to AIDevOps home
🌐

nGrinder Practical Examples

Examples for the Controller-Agent setup, Groovy scripts, and Docker deployment.

View practical examples →

Contents

0 / 7
  1. What is nGrinder?
  2. Architecture
  3. Installing with Docker
  4. Writing Groovy scripts
  5. Running a test
  6. Monitoring & reports
  7. Practical tips
Contents 7 sections
  1. What is nGrinder?
  2. Architecture
  3. Installing with Docker
  4. Writing Groovy scripts
  5. Running a test
  6. Monitoring & reports
  7. Practical tips

What is nGrinder?

nGrinder is an enterprise-grade distributed load testing platform that Naver built on the Grinder framework. It is used to validate the performance of large-scale services in Korea.

FeatureDescription
Web UIDesign ¡ run ¡ monitor tests in the browser
Distributed architectureGenerate large-scale load with a Controller + many Agents
Groovy/JythonBuild complex scenarios with JVM-based scripts
Script recordingRecord real user behavior automatically through an HTTP proxy

Architecture

  • Controller: serves the web UI, schedules tests, and aggregates results
  • Agent: the worker process that generates the actual load
  • Target Server: the server under test

Connecting several Agents to one Controller allows horizontal scaling.

Installing with Docker

docker-compose.ymlYAML
version: '3'
services:
  controller:
    image: ngrinder/controller:3.5.9
    ports:
      - "8080:8080"
      - "16001:16001"
      - "12000-12009:12000-12009"
    volumes:
      - ./ngrinder-home:/opt/ngrinder-controller

  agent:
    image: ngrinder/agent:3.5.9
    links:
      - controller
    environment:
      - CONTROLLER_ADDR=controller
BASH
docker-compose up -d
# Open http://localhost:8080
# Default account: admin / admin
💡

To run several Agents, scale out the agent service: docker-compose up --scale agent=3 -d

Writing Groovy scripts

BasicTest.groovyGROOVY
import static net.grinder.script.Grinder.grinder
import static org.junit.Assert.*
import static org.hamcrest.Matchers.*
import net.grinder.script.GTest
import net.grinder.plugin.http.HTTPRequest
import net.grinder.plugin.http.HTTPPluginControl

def test1 = new GTest(1, "API Test")
def request = new HTTPRequest()

test1.record(request)

class TestRunner {
  public void __call__() {
    def response = request.GET("https://httpbin.org/get")

    assertThat(response.statusCode, is(200))
    grinder.logger.info("Response: ${response.text}")
  }
}

POST request + JSON body

GROOVY
import net.grinder.plugin.http.HTTPRequest
import HTTPClient.NVPair

def request = new HTTPRequest()
def headers = [new NVPair("Content-Type", "application/json")] as NVPair[]

class TestRunner {
  void __call__() {
    def body = '{"username": "user1", "password": "pass1"}'
    def response = request.POST(
      "https://api.example.com/login",
      body.bytes,
      headers
    )
    assert response.statusCode == 200
  }
}

Running a test

  1. Upload or write a script in the Script menu
  2. Click New Test in the Performance Test menu
  3. Set the number of Agents, VUsers per Agent, and the test duration
  4. Select the script and click Start Test

While the test runs you can monitor TPS, mean response time, and error rate in real time.

Monitoring & reports

An HTML report is generated automatically when the test finishes. Key metrics:

  • TPS (Transactions Per Second): transactions processed per second
  • Mean Time: mean response time (ms)
  • Peak TPS: maximum TPS
  • Error Rate: error rate (%)

Practical tips

â„šī¸

Tune Agent memory: raise the JVM heap with -Xms512m -Xmx1024m in the Agent settings to handle more VUsers.

âš ī¸

Putting the Controller, Agents, and Target Server on the same machine will not give accurate results. Always separate them.