This contains the installation guide for nGrinder 3.3 or later. If you want to see the previous version's installation guide, Please visit Installation Guide - version 3.2
This guide shows how to install nGrinder 3.3 or later.
You can download nGridner controller from the following link.
nGrinder is distributed as a self executable web archive file(WAR) file just like Jenkins, you can put this archive file into your familar web application server (like Tomcat) or run the package in the command line.
Be careful, Never locate the war file in the space containing folder like "C:\Program Files\Tomcat\webapps\".
java -jar ngrinder-controller-X.X.war
nGrinder needs quite big perm-gen memory. Please run nGrinder with the following command. java -XX:MaxPermSize=200m -jar ngrinder-controller-3.3.war
java -XX:MaxPermSize=200m -jar ngrinder-controller-3.3.war --port 80
INFO 14. 1. 20 오후 4:39:liquibase: ChangeSet ngrinder_datachange_logfile/db.changelog_schema_22.xml::22::ngrinder.3.3 r an successfully in 4ms INFO 14. 1. 20 오후 4:39:liquibase: ChangeSet ngrinder_datachange_logfile/db.changelog_schema_23.xml::23::ngrinder.3.3 r an successfully in 7ms INFO 14. 1. 20 오후 4:39:liquibase: ChangeSet ngrinder_datachange_logfile/db.changelog_schema_24.xml::24::ngrinder.3.3 r an successfully in 2ms INFO 14. 1. 20 오후 4:39:liquibase: ChangeSet ngrinder_datachange_logfile/db.changelog_schema_25.xml::25::ngrinder.3.3 r an successfully in 7ms INFO 14. 1. 20 오후 4:39:liquibase: ChangeSet ngrinder_datachange_logfile/db.changelog_schema_26.xml::26::ngrinder.3.3 r an successfully in 8ms 2014-01-20 16:39:30.633:INFO:/:Initializing Spring FrameworkServlet 'appServlet' 2014-01-20 16:39:31.141:INFO::Started SocketConnector@@0.0.0.0:8080
JAVA_OPTS="-Xms600m -Xmx1024m -XX:MaxPermSize=200m" # for catalina.sh
set JAVA_OPTS=-Xms600m -Xmx1024m -XX:MaxPermSize=200m # for catalina.bat
Not like previous nGrinder, nGrinder 3.3 agents is downloaded from the controller. The downloaded agent package already contains the default agent configuration connecting to the controller from which the agent is downloaded.
So just unpacking the tar file and running “run_agent.sh” or “run_agent.bat” make the agent connect to the controller.
Because you’re logged in as admin, the downloadable agent package contains the configurations which let the agents shared by all user.
If you logged in as not admin account, the link is changed to “Download Private Agent” containning the configurations which let the agents only occupied by the current user.
See Private Agent for details.
run_agent.sh -o # for linux / macor
run_agent_bg.sh -o # If you want to run it in the background for linux / mac
run_agent.bat –o # for windows
stop_agent.sh # for linux / macor
stop_agent.bat # for windows
controller.enable_agent_auto_approval=trueconfiguration in the controller configuration, You have to approve agents by yourself.
> ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30676 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 16000 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 10240 cpu time (seconds, -t) unlimited max user processes (-u) 32768 virtual memory (kbytes, -v) unlimited file locks (-x) unlimitedIf your machine has small "max user processes" and "open files" entry when you run "ulimit -a", please make it at least over 10000. Open /etc/security/limits.conf file in the root account and add followings.
your_account soft nproc 32768 your_account hard nproc 32768 root soft nproc 32768 root hard nproc 32768 your_account soft nofile 16000 your_account hard nofile 16000 root soft nofile 16000 root hard nofile 16000
By default, the only one agent per machine is supported. However if you want to run multiple agents in a single machine, you have to configure some agent option. Please refer Agent Configuration Guide.
nGrinder Monitor is the subset of the agent package and is installed into target machine to collect system statistics(such as CPU, MEM and Network) under the loads.
You can download monitors from the controller as well.
run_monitor_bg.sh # for linux / macor
run_monitor.bat # for windows
stop_monitor.sh # for linux / macor
stop_monitor.bat –o # for windows