Am 05.11.20 um 13:53 schrieb Jmeter Tea: > The documentation about executing jmeter in linux isn't clear, > > What should be used in CLI? What JVM settings are problematic in each case?
Looking at the history of those two files, it seems, that jmeter.sh was intended as a simple showcase and jmeter as the normal start script. The jmeter.sh file grew to almost the size and complexity of the jmeter script, but ended to be a wrapper of it. Currently jmeter.sh sets a few variables and calls jmeter internally. I use bin/jmeter exclusively and don't know, whether anyone use the jmeter.sh script. > > Spec: > > Un*x script files; should work on most Linux/Unix systems: > jmeterrun JMeter (in GUI mode by default). Defines some JVM settings which > may not work for all JVMs.jmeter.shvery basic JMeter script (You may need > to adapt JVM options like memory settings). If you start reading bin/jmeter from the bottom up, you will see, that there is an environment variable JMETER_COMPLETE_ARGS, which can be set to disable the generation of the internal ARGS environment variable. That variable is used by bin/jmeter.sh, but you can use it, too. This will disable all the special handling for memory settings, language settings or Java 9 module setup. You can specify whatever you want via the enviroment variables JVM_ARGS or JMETER_OPTS. JMETER_OPTS will be enhanced with MacOS specific stuff, if you run the shell script on MacOS. If you want to get rid of the memory specifc stuff, you can set the environment variables GC_ALGO and HEAP. They will get combined into the variable ARGS (if JMETER_COMPLETE_ARGS is NOT set) and then used to run JMeter. > Also why setenv.sh isn't called in jmeter.sh? setenv.sh is sourced into bin/jmeter, which is called by bin/jmeter.sh so it will (or at least should) be called. Is there any specific reason for your question? Where did you look for information? Felix > > Thank you > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
