[
https://issues.jboss.org/browse/WFLY-5822?page=com.atlassian.jira.plugin....
]
Richard Achmatowicz edited comment on WFLY-5822 at 1/19/16 11:12 AM:
---------------------------------------------------------------------
All the memory stats collected by the driver node are being reported as null:
{noformat}
2016/01/19 09:52:04:632 EST [DEBUG][Thread-7] HOST
perf29.mw.lab.eng.bos.redhat.com:rootProcess:c - Aggregated stats: [perf32.youngGen:
null,perf32.survivorGen: null,perf32.tenuredGen: null,perf32.permGen:
null,perf32.memTotal: null,perf33.youngGen: null,perf33.survivorGen:
null,perf33.tenuredGen: null,perf33.permGen: null,perf33.memTotal: null,perf29.count: 4]
{noformat}
Is this broken? It seems to be as I see the same issue in earlier test runs. This should
be fixed as server side memory issues are a potential cause for concern.
was (Author: rachmato):
All the memory stats collected by the driver node are being reported as null:
{noformat}
2016/01/19 09:52:04:632 EST [DEBUG][Thread-7] HOST
perf29.mw.lab.eng.bos.redhat.com:rootProcess:c - Aggregated stats: [perf32.youngGen:
null,perf32.survivorGen: null,perf32.tenuredGen: null,perf32.permGen:
null,perf32.memTotal: null,perf33.youngGen: null,perf33.survivorGen:
null,perf33.tenuredGen: null,perf33.permGen: null,perf33.memTotal: null,perf29.count: 4]
{noformat}
Is this broken?
Clustering performance regression in ejbremote-dist-sync scenario
------------------------------------------------------------------
Key: WFLY-5822
URL:
https://issues.jboss.org/browse/WFLY-5822
Project: WildFly
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 10.0.0.CR5
Reporter: Michal Vinkler
Assignee: Richard Achmatowicz
Priority: Critical
Compared to EAP 6, all SYNC scenarios have the same/better performance except of this
one, wonder why?
Compare these results:
stress-ejbremote-dist-sync
7.0.0.ER2:
[
throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...]
6.4.0.GA:
[
throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...]
---------------------------------------
Just for comparison: ejbremote REPL_SYNC scenario *performs well* on the other hand:
stress-ejbremote-repl-sync
7.0.0.ER2:
[
throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-str...]
6.4.0.GA:
[
throughput|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-str...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)