[
https://issues.apache.org/jira/browse/GEODE-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774543#comment-16774543
]
Barry Oglesby edited comment on GEODE-6435 at 2/21/19 10:13 PM:
----------------------------------------------------------------
I wrote a simple test that just creates 500 connections to a server.
With no heap settings, I see pretty much the same heap usage as JDK 8.
With these heap settings (which are what dunit jvms use): {{-Xms512m -Xmx512m
-XX:MetaspaceSize=512m -XX:SoftRefLRUPolicyMSPerMB=1}}, I see double the heap
usage (which causes the OOME).
No heap settings:
Live histogram:
{noformat}
num #instances #bytes class name (module)
-------------------------------------------------------
1: 33610 268237040 [B ([email protected])
2: 4441 1618264 [I ([email protected])
3: 30274 726576 java.lang.String ([email protected])
4: 5664 684952 java.lang.Class ([email protected])
5: 7556 417352 [Ljava.lang.Object; ([email protected])
6: 618 368872 [J ([email protected])
7: 10848 347136 java.util.concurrent.ConcurrentHashMap$Node ([email protected])
8: 10114 323648 java.util.HashMap$Node ([email protected])
9: 2130 220952 [Ljava.util.HashMap$Node; ([email protected])
10: 2373 208824 java.lang.reflect.Method ([email protected])
Total 188802 276340528
{noformat}
vsd:
{noformat}
currentMaxMemory=8,589,934,592
currentUsedMemory=279,838,728
{noformat}
With heap settings:
Live histogram:
{noformat}
num #instances #bytes class name (module)
-------------------------------------------------------
1: 30977 266997720 [B ([email protected])
2: 4934 262202008 [I ([email protected])
3: 28018 672432 java.lang.String ([email protected])
4: 5435 659304 java.lang.Class ([email protected])
5: 614 367784 [J ([email protected])
6: 11023 352736 java.util.concurrent.ConcurrentHashMap$Node ([email protected])
7: 4969 335792 [Ljava.lang.Object; ([email protected])
8: 9651 308832 java.util.HashMap$Node ([email protected])
9: 1728 180440 [Ljava.util.HashMap$Node; ([email protected])
10: 1464 128832 java.lang.reflect.Method ([email protected])
Total 165373 534770560
{noformat}
vsd:
{noformat}
currentMaxMemory=536,870,912
currentUsedMemory=535,659,832
{noformat}
was (Author: barry.oglesby):
I wrote a simple test that just creates 500 connections to a server.
With no heap settings, I see pretty much the same heap usage as JDK 8.
With these heap settings (which are what dunit jvms use): {{-Xms512m -Xmx512m
-XX:MetaspaceSize=512m -XX:SoftRefLRUPolicyMSPerMB=1}}, I see double the heap
usage (which causes the OOME).
No heap settings:
Live histogram:
{noformat}
num #instances #bytes class name (module)
-------------------------------------------------------
1: 33610 268237040 [B ([email protected])
2: 4441 1618264 [I ([email protected])
3: 30274 726576 java.lang.String ([email protected])
4: 5664 684952 java.lang.Class ([email protected])
5: 7556 417352 [Ljava.lang.Object; ([email protected])
6: 618 368872 [J ([email protected])
7: 10848 347136 java.util.concurrent.ConcurrentHashMap$Node ([email protected])
8: 10114 323648 java.util.HashMap$Node ([email protected])
9: 2130 220952 [Ljava.util.HashMap$Node; ([email protected])
10: 2373 208824 java.lang.reflect.Method ([email protected])
Total 188802 276340528\{noformat}
vsd:
{noformat}
currentMaxMemory=8,589,934,592
currentUsedMemory=279,838,728\{noformat}
With heap settings:
Live histogram:
{noformat}
num #instances #bytes class name (module)
-------------------------------------------------------
1: 30977 266997720 [B ([email protected])
2: 4934 262202008 [I ([email protected])
3: 28018 672432 java.lang.String ([email protected])
4: 5435 659304 java.lang.Class ([email protected])
5: 614 367784 [J ([email protected])
6: 11023 352736 java.util.concurrent.ConcurrentHashMap$Node ([email protected])
7: 4969 335792 [Ljava.lang.Object; ([email protected])
8: 9651 308832 java.util.HashMap$Node ([email protected])
9: 1728 180440 [Ljava.util.HashMap$Node; ([email protected])
10: 1464 128832 java.lang.reflect.Method ([email protected])
Total 165373 534770560\{noformat}
vsd:
{noformat}
currentMaxMemory=536,870,912
currentUsedMemory=535,659,832\{noformat}
> CI Failure: SerialGatewaySenderQueueDUnitTest.testCreateMaximumSenders
> assertion fails
> --------------------------------------------------------------------------------------
>
> Key: GEODE-6435
> URL: https://issues.apache.org/jira/browse/GEODE-6435
> Project: Geode
> Issue Type: Bug
> Reporter: Patrick Rhomberg
> Assignee: Barry Oglesby
> Priority: Major
> Attachments: jdk11_OldGen_usedMemory_failure.gif,
> jdk11_OldGen_usedMemory_success.gif, jdk8_OldGen_usedMemory_success.gif
>
>
> {noformat}
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueueDUnitTest
> > testCreateMaximumSenders FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueueDUnitTest$$Lambda$390/0x0000000840596840.run
> in VM 2 running on Host 2e6d9f20266c with 8 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueueDUnitTest.testCreateMaximumSenders(SerialGatewaySenderQueueDUnitTest.java:370)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition with lambda
> expression in org.apache.geode.internal.cache.wan.WANTestBase that uses long
> was not fulfilled within 300 seconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:79)
> at
> org.awaitility.core.CallableCondition.await(CallableCondition.java:27)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:860)
> at
> org.apache.geode.internal.cache.wan.WANTestBase.verifyListenerEvents(WANTestBase.java:3542)
> at
> org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderQueueDUnitTest.lambda$testCreateMaximumSenders$faf964a3$1(SerialGatewaySenderQueueDUnitTest.java:370)
> java.lang.AssertionError: An exception occurred during asynchronous
> invocation.
> Caused by:
> java.rmi.ConnectIOException: error during JRMP connection
> establishment; nested exception is:
> java.net.SocketTimeoutException: Read timed out
> Caused by:
> java.net.SocketTimeoutException: Read timed out
> {noformat}
>
> See pipeline failure here:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/413]
> Find test results here:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-SNAPSHOT.0456/test-results/distributedTest/1550631451/]
> Find artifacts here:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-SNAPSHOT.0456/test-artifacts/1550631451/distributedtestfiles-OpenJDK11-1.9.0-SNAPSHOT.0456.tgz]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
