Jmeter startup consuming 14g memory in non gui mode without usage of any listener
0
I am using Jmeter in non GUI and not using any listener as of now. Jmeter is taking 14 g of memory at the time of start up in 4.0 version and 9g of memory in 5.0 version with out passing any configuration file and as the load is increasing (in 1 sec 250 request with loop count of 100) memory utilization is 32g. I do not want to increase heap size, can you tell me the solution how i can reduce the memory consumption?
Virtual memory usgae through top command
Simple jmx file
java jmeter heap
asked Nov 27 '18 at 7:20
RuchikaRuchika
43
add a comment |
0
I am using Jmeter in non GUI and not using any listener as of now. Jmeter is taking 14 g of memory at the time of start up in 4.0 version and 9g of memory in 5.0 version with out passing any configuration file and as the load is increasing (in 1 sec 250 request with loop count of 100) memory utilization is 32g. I do not want to increase heap size, can you tell me the solution how i can reduce the memory consumption?
Virtual memory usgae through top command
Simple jmx file
java jmeter heap
asked Nov 27 '18 at 7:20
RuchikaRuchika
43
add a comment |
0
0
0
I am using Jmeter in non GUI and not using any listener as of now. Jmeter is taking 14 g of memory at the time of start up in 4.0 version and 9g of memory in 5.0 version with out passing any configuration file and as the load is increasing (in 1 sec 250 request with loop count of 100) memory utilization is 32g. I do not want to increase heap size, can you tell me the solution how i can reduce the memory consumption?
Virtual memory usgae through top command
Simple jmx file
java jmeter heap
asked Nov 27 '18 at 7:20
RuchikaRuchika
43
I am using Jmeter in non GUI and not using any listener as of now. Jmeter is taking 14 g of memory at the time of start up in 4.0 version and 9g of memory in 5.0 version with out passing any configuration file and as the load is increasing (in 1 sec 250 request with loop count of 100) memory utilization is 32g. I do not want to increase heap size, can you tell me the solution how i can reduce the memory consumption?
Virtual memory usgae through top command
Simple jmx file
java jmeter heap
java jmeter heap
asked Nov 27 '18 at 7:20
RuchikaRuchika
43
asked Nov 27 '18 at 7:20
RuchikaRuchika
43
edited Nov 27 '18 at 10:06
Ruchika
asked Nov 27 '18 at 7:20
RuchikaRuchika
43
asked Nov 27 '18 at 7:20
RuchikaRuchika
43
asked Nov 27 '18 at 7:20
RuchikaRuchika
43
43
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
0
Most probably you cannot as heap utilization depends on the nature of your test, request and response sizes, number of Pre/Post Processors/Assertions, etc.
- Make sure to follow JMeter Best Practices
- Consider using a profiler tool i.e. JVisualVM or JProfiler or Heap Dump / Heap Analyzer to figure out which component(s) is consuming the heap
- If you don't have enough RAM and suffer from intensive GC activities the only way of speeding your test up is going for distributed testing - this way you will be able to decrease the number of threads for each JMeter engine.
answered Nov 27 '18 at 9:00
Dmitri TDmitri T
72.6k33662
It is taking too much swap memory if we run command sh jmeter -n -e or sh jmeter -n -t test.jmx(in jmx file we are using only user thread group with 1 thread in 1 sec with loop count 1 only) and at the same time if we use top command it will show the virtual memory utilization that is 14g that is too much for 1 request.
– Ruchika
Nov 27 '18 at 9:43
It might be the case that either somewhere injmeterstartup script you have-Xmsargument or there isJVM_ARGSenvironment variable which is being consumed by the script. You can try out launching JMeter asjava -jar ApacheJMeter.jar -n -t test.jmxand the heap usage should go down.
– Dmitri T
Nov 27 '18 at 9:56
I added sample images for simple jmx file and top command results.
– Ruchika
Nov 27 '18 at 10:09
I run this java -jar ApacheJMeter.jar -n -t test.jmx and checked through top command , virtual memory usage increased to 36g for version 4.0
– Ruchika
Nov 28 '18 at 13:39
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53494571%2fjmeter-startup-consuming-14g-memory-in-non-gui-mode-without-usage-of-any-listene%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
Most probably you cannot as heap utilization depends on the nature of your test, request and response sizes, number of Pre/Post Processors/Assertions, etc.
- Make sure to follow JMeter Best Practices
- Consider using a profiler tool i.e. JVisualVM or JProfiler or Heap Dump / Heap Analyzer to figure out which component(s) is consuming the heap
- If you don't have enough RAM and suffer from intensive GC activities the only way of speeding your test up is going for distributed testing - this way you will be able to decrease the number of threads for each JMeter engine.
answered Nov 27 '18 at 9:00
Dmitri TDmitri T
72.6k33662
It is taking too much swap memory if we run command sh jmeter -n -e or sh jmeter -n -t test.jmx(in jmx file we are using only user thread group with 1 thread in 1 sec with loop count 1 only) and at the same time if we use top command it will show the virtual memory utilization that is 14g that is too much for 1 request.
– Ruchika
Nov 27 '18 at 9:43
It might be the case that either somewhere injmeterstartup script you have-Xmsargument or there isJVM_ARGSenvironment variable which is being consumed by the script. You can try out launching JMeter asjava -jar ApacheJMeter.jar -n -t test.jmxand the heap usage should go down.
– Dmitri T
Nov 27 '18 at 9:56
I added sample images for simple jmx file and top command results.
– Ruchika
Nov 27 '18 at 10:09
I run this java -jar ApacheJMeter.jar -n -t test.jmx and checked through top command , virtual memory usage increased to 36g for version 4.0
– Ruchika
Nov 28 '18 at 13:39
add a comment |
0
Most probably you cannot as heap utilization depends on the nature of your test, request and response sizes, number of Pre/Post Processors/Assertions, etc.
- Make sure to follow JMeter Best Practices
- Consider using a profiler tool i.e. JVisualVM or JProfiler or Heap Dump / Heap Analyzer to figure out which component(s) is consuming the heap
- If you don't have enough RAM and suffer from intensive GC activities the only way of speeding your test up is going for distributed testing - this way you will be able to decrease the number of threads for each JMeter engine.
answered Nov 27 '18 at 9:00
Dmitri TDmitri T
72.6k33662
It is taking too much swap memory if we run command sh jmeter -n -e or sh jmeter -n -t test.jmx(in jmx file we are using only user thread group with 1 thread in 1 sec with loop count 1 only) and at the same time if we use top command it will show the virtual memory utilization that is 14g that is too much for 1 request.
– Ruchika
Nov 27 '18 at 9:43
It might be the case that either somewhere injmeterstartup script you have-Xmsargument or there isJVM_ARGSenvironment variable which is being consumed by the script. You can try out launching JMeter asjava -jar ApacheJMeter.jar -n -t test.jmxand the heap usage should go down.
– Dmitri T
Nov 27 '18 at 9:56
I added sample images for simple jmx file and top command results.
– Ruchika
Nov 27 '18 at 10:09
I run this java -jar ApacheJMeter.jar -n -t test.jmx and checked through top command , virtual memory usage increased to 36g for version 4.0
– Ruchika
Nov 28 '18 at 13:39
add a comment |
0
0
0
Most probably you cannot as heap utilization depends on the nature of your test, request and response sizes, number of Pre/Post Processors/Assertions, etc.
- Make sure to follow JMeter Best Practices
- Consider using a profiler tool i.e. JVisualVM or JProfiler or Heap Dump / Heap Analyzer to figure out which component(s) is consuming the heap
- If you don't have enough RAM and suffer from intensive GC activities the only way of speeding your test up is going for distributed testing - this way you will be able to decrease the number of threads for each JMeter engine.
answered Nov 27 '18 at 9:00
Dmitri TDmitri T
72.6k33662
Most probably you cannot as heap utilization depends on the nature of your test, request and response sizes, number of Pre/Post Processors/Assertions, etc.
- Make sure to follow JMeter Best Practices
- Consider using a profiler tool i.e. JVisualVM or JProfiler or Heap Dump / Heap Analyzer to figure out which component(s) is consuming the heap
- If you don't have enough RAM and suffer from intensive GC activities the only way of speeding your test up is going for distributed testing - this way you will be able to decrease the number of threads for each JMeter engine.
answered Nov 27 '18 at 9:00
Dmitri TDmitri T
72.6k33662
answered Nov 27 '18 at 9:00
Dmitri TDmitri T
72.6k33662
answered Nov 27 '18 at 9:00
Dmitri TDmitri T
72.6k33662
answered Nov 27 '18 at 9:00
Dmitri TDmitri T
72.6k33662
72.6k33662
It is taking too much swap memory if we run command sh jmeter -n -e or sh jmeter -n -t test.jmx(in jmx file we are using only user thread group with 1 thread in 1 sec with loop count 1 only) and at the same time if we use top command it will show the virtual memory utilization that is 14g that is too much for 1 request.
– Ruchika
Nov 27 '18 at 9:43
It might be the case that either somewhere injmeterstartup script you have-Xmsargument or there isJVM_ARGSenvironment variable which is being consumed by the script. You can try out launching JMeter asjava -jar ApacheJMeter.jar -n -t test.jmxand the heap usage should go down.
– Dmitri T
Nov 27 '18 at 9:56
I added sample images for simple jmx file and top command results.
– Ruchika
Nov 27 '18 at 10:09
I run this java -jar ApacheJMeter.jar -n -t test.jmx and checked through top command , virtual memory usage increased to 36g for version 4.0
– Ruchika
Nov 28 '18 at 13:39
add a comment |
It is taking too much swap memory if we run command sh jmeter -n -e or sh jmeter -n -t test.jmx(in jmx file we are using only user thread group with 1 thread in 1 sec with loop count 1 only) and at the same time if we use top command it will show the virtual memory utilization that is 14g that is too much for 1 request.
– Ruchika
Nov 27 '18 at 9:43
It might be the case that either somewhere injmeterstartup script you have-Xmsargument or there isJVM_ARGSenvironment variable which is being consumed by the script. You can try out launching JMeter asjava -jar ApacheJMeter.jar -n -t test.jmxand the heap usage should go down.
– Dmitri T
Nov 27 '18 at 9:56
I added sample images for simple jmx file and top command results.
– Ruchika
Nov 27 '18 at 10:09
I run this java -jar ApacheJMeter.jar -n -t test.jmx and checked through top command , virtual memory usage increased to 36g for version 4.0
– Ruchika
Nov 28 '18 at 13:39
It is taking too much swap memory if we run command sh jmeter -n -e or sh jmeter -n -t test.jmx(in jmx file we are using only user thread group with 1 thread in 1 sec with loop count 1 only) and at the same time if we use top command it will show the virtual memory utilization that is 14g that is too much for 1 request.
– Ruchika
Nov 27 '18 at 9:43
It is taking too much swap memory if we run command sh jmeter -n -e or sh jmeter -n -t test.jmx(in jmx file we are using only user thread group with 1 thread in 1 sec with loop count 1 only) and at the same time if we use top command it will show the virtual memory utilization that is 14g that is too much for 1 request.
– Ruchika
Nov 27 '18 at 9:43
It might be the case that either somewhere in
jmeter startup script you have -Xms argument or there is JVM_ARGS environment variable which is being consumed by the script. You can try out launching JMeter as java -jar ApacheJMeter.jar -n -t test.jmx and the heap usage should go down.– Dmitri T
Nov 27 '18 at 9:56
It might be the case that either somewhere in
jmeter startup script you have -Xms argument or there is JVM_ARGS environment variable which is being consumed by the script. You can try out launching JMeter as java -jar ApacheJMeter.jar -n -t test.jmx and the heap usage should go down.– Dmitri T
Nov 27 '18 at 9:56
I added sample images for simple jmx file and top command results.
– Ruchika
Nov 27 '18 at 10:09
I added sample images for simple jmx file and top command results.
– Ruchika
Nov 27 '18 at 10:09
I run this java -jar ApacheJMeter.jar -n -t test.jmx and checked through top command , virtual memory usage increased to 36g for version 4.0
– Ruchika
Nov 28 '18 at 13:39
I run this java -jar ApacheJMeter.jar -n -t test.jmx and checked through top command , virtual memory usage increased to 36g for version 4.0
– Ruchika
Nov 28 '18 at 13:39
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53494571%2fjmeter-startup-consuming-14g-memory-in-non-gui-mode-without-usage-of-any-listene%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
