Bug 61555 - Metaspace should be restricted as default
Summary: Metaspace should be restricted as default
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 3.2
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
Depends on:
Reported: 2017-09-21 11:09 UTC by Justin McCartney
Modified: 2017-10-28 14:45 UTC (History)
2 users (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Justin McCartney 2017-09-21 11:09:12 UTC
For Jmeter 3.2, the metaspace maximum size is not set by default in the Jmeter scripts.  This can lead to situations where tests will fail or start to slow after a large number of hours into the test, due to using up all available memory on the box and invoking paging.

It is preferable that Jmeter specify a default value for max metaspace to prevent this happening.  If my tests are going to fail it is better that they will fail early, rather than later and with a OOM metaspace, rather than showing degraded performance which may be assumed to be related to the app under test.

I would leave it to the team to decide what the default max should be.  Obviously this might break some user's current tests so it will need to be highlighted in the release notes.  We currently restrict our Jmeters to 256mb on our 4GB boxes.
Comment 1 Philippe Mouawad 2017-10-28 14:45:35 UTC
Author: pmouawad
Date: Thu Sep 28 19:19:03 2017
New Revision: 1810036

URL: http://svn.apache.org/viewvc?rev=1810036&view=rev
Add MaxMetaspaceSize

Comment 2 The ASF infrastructure team 2022-09-24 20:38:10 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4502