https://bz.apache.org/bugzilla/show_bug.cgi?id=63565
Bug ID: 63565
Summary: GC issue with Jmeter during the endurance run
Product: JMeter
Version: 5.1
Hardware: PC
OS: Solaris
Status: NEW
Severity: normal
Priority: P2
Component: Main
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: JMETER_5.2
Created attachment 36656
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36656&action=edit
JmeterGCLog
Hi,
We have been testing couchbase DB performance with Jmeter-5.1 and we are
experiencing the GC issue(YGC). we didn't hit with with a memory leak and our
Tenured space is completely flat throughout the run.
Machine Spec:
GNU/Linux x86_64 (64 bit)
RAM ~16 GB
Disk 60 GB
Processor 6 Core
Jmeter Info:
Version: 5.1
Heap Size: 6 GB
GC: G1 (Default)
1. Run was conducted for 4 hours
2. 1 Load generator was used to push data to Couchbase database
3. The 95th percentile RT is 1ms.
4. Our Objects are short lived and none of it gets promoted to Tenured space.
5. We see a increased time consumption of Young GC time during the endurance
run
6. Exactly after 2.30 hours of run, The G1 reallocates the memory size within
the heap. i.e, it shrinks the Young generation and Increases the Tenure space
7. From there on we see a spike in our RT. We don't see any issue with
Couchbase side but with the Jmeter on clearing the objects time. Its
exponentially growing along with the run
8. We have executed one more round of test by enabling the verbose gc log. What
we found is that most of the time were spent in the Ref Proc.
Attaching the screenshot as well as the gc log for your reference.
--
You are receiving this mail because:
You are the assignee for the bug.
