[JBoss JIRA] (WFLY-9835) Performance issues in WildFly11 as my 90% for jmeter run gets increased to 2x for same set of run as it was in Jboss.
by nilesh ratta (JIRA)
[ https://issues.jboss.org/browse/WFLY-9835?page=com.atlassian.jira.plugin.... ]
nilesh ratta updated WFLY-9835:
-------------------------------
Description:
I have upgraded my application from Jboss6 with java 6 to WildFly11 with java 8 in dev environment.
Note :
I am facing some performance issues in WildFly11 as my 90% gets increased for same set of run as it was in Jboss.
*And minor GC gets increased to 7 times as it was in jboss.*
And there is no application level code changes in wildfly11.
*Please find attached files for GC log and Heap dump related inputs.*
Inputs :
JVM parameters : Parallel GC with 4 threads , -Xmx6144m Xmx6144m -XX:NewRatio=1 -XX:ParallelGCThreads=4 -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m
Parameters are same in Jboss 6 and WildFly11.
Jmeter result overview for 100 users in 15 mnts with 250 sec rampup time.
As all of our app server is on AWS with same configuration.
1. Jboss 6 results :
Label Count Average 90%_line Min Max Error% ThroughPut
TOTAL 48664 167 418 0 30374 0 53.80
2. WildFLy11 results :
Label Count Average 90%_line Min Max Error% ThroughPut
TOTAL 54775 287 887 0 14286 0 60.672
Note : As my count nd throughput increases but my* 90% is > 2x * for WildFly11.
Kindly find the attached files for Heap dump as follows with following names in .png format:-
For WildFly 11 :
1. W_img1.png :-
WildFly11_DominatorTree : io.netty.buffer.PoolChunk ?????
2. W_img2.png
WildFly_Histogram : Class Name| Objects | Shallow Heap | Retained Heap
byte[] | 53,925 | 163,144,832 | >= 163,144,832
3. W_img3.png
WildFly_Immediate Dominators for byte [] :
For Jboss -6
1. J_img1.png :-
Jboss6_DominatorTree : as there is no io.netty.buffer.PoolChunk .....
2. J_img2.png :-
Jboss6_Histogram
3. J_img3.png :
Jboss6_Immediate Dominators for byte [] :
Kindly find GC log images for wildFly 11 and jboss 6 .for 15 mnts load run .
Wildfly 11 ------------ Jboss 6
Total GC :-------- 1167 ------------- 174
Total GC Time :-------- >21 sec ------------- 6 sec
Total Reclaimed Bytes :------ 3.32 tb ------------ 480 gb
was:
I have upgraded my application from Jboss6 with java 6 to WildFly11 with java 8 in dev environment.
Note :
I am facing some performance issues in WildFly11 as my 90% gets increased for same set of run as it was in Jboss.
*And minor GC gets increased to 7 times as it was in jboss.*
And there is no application level code changes in wildfly11.
*Please find attached files for GC log and Heap dump related inputs.*
Inputs :
JVM parameters : Parallel GC with 4 threads , -Xmx6144m Xmx6144m -XX:NewRatio=1 -XX:ParallelGCThreads=4 -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m
Parameters are same in Jboss 6 and WildFly11.
Jmeter result overview for 100 users in 15 mnts with 250 sec rampup time.
As all of our app server is on AWS with same configuration.
1. Jboss 6 results :
Label Count Average 90%_line Min Max Error% ThroughPut
TOTAL 48664 167 418 0 30374 0 53.80
2. WildFLy11 results :
Label Count Average 90%_line Min Max Error% ThroughPut
TOTAL 54775 287 887 0 14286 0 60.672
Note : As my count nd throughput increases but my* 90% is > 2x * for WildFly11.
Kindly find the attached files for Heap dump as follows with following names in .png format:-
For WildFly 11 :
1. W_img1.png :-
WildFly11_DominatorTree : io.netty.buffer.PoolChunk ?????
2. W_img2.png
WildFly_Histogram : Class Name| Objects | Shallow Heap | Retained Heap
byte[] | 53,925 | 163,144,832 | >= 163,144,832
3. W_img3.png
WildFly_Immediate Dominators for byte [] :
For Jboss -6
1. J_img1.png :-
Jboss6_DominatorTree : as there is no io.netty.buffer.PoolChunk .....
2. J_img2.png :-
Jboss6_Histogram
3. J_img3.png :
Jboss6_Immediate Dominators for byte [] :
Kindly find GC log images for wildFly 11 and jboss 6 .for 15 mnts load run .
Wildfly 11 Jboss 6
Total GC 1162 174
Total GC Time >21 sec 6 sec
Total Reclaimed Bytes 3.32 tb 480 gb
> Performance issues in WildFly11 as my 90% for jmeter run gets increased to 2x for same set of run as it was in Jboss.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9835
> URL: https://issues.jboss.org/browse/WFLY-9835
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Server
> Reporter: nilesh ratta
> Assignee: Jason Greene
> Attachments: J-img3.png, J_img1.png, J_img2.png, Jboss_GClog.png, W_img1.png, W_img2.png, W_img3.png, WildFly11_GCLog.png
>
>
> I have upgraded my application from Jboss6 with java 6 to WildFly11 with java 8 in dev environment.
> Note :
> I am facing some performance issues in WildFly11 as my 90% gets increased for same set of run as it was in Jboss.
> *And minor GC gets increased to 7 times as it was in jboss.*
> And there is no application level code changes in wildfly11.
> *Please find attached files for GC log and Heap dump related inputs.*
> Inputs :
> JVM parameters : Parallel GC with 4 threads , -Xmx6144m Xmx6144m -XX:NewRatio=1 -XX:ParallelGCThreads=4 -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m
> Parameters are same in Jboss 6 and WildFly11.
> Jmeter result overview for 100 users in 15 mnts with 250 sec rampup time.
> As all of our app server is on AWS with same configuration.
> 1. Jboss 6 results :
> Label Count Average 90%_line Min Max Error% ThroughPut
> TOTAL 48664 167 418 0 30374 0 53.80
> 2. WildFLy11 results :
> Label Count Average 90%_line Min Max Error% ThroughPut
> TOTAL 54775 287 887 0 14286 0 60.672
> Note : As my count nd throughput increases but my* 90% is > 2x * for WildFly11.
> Kindly find the attached files for Heap dump as follows with following names in .png format:-
> For WildFly 11 :
> 1. W_img1.png :-
> WildFly11_DominatorTree : io.netty.buffer.PoolChunk ?????
> 2. W_img2.png
> WildFly_Histogram : Class Name| Objects | Shallow Heap | Retained Heap
> byte[] | 53,925 | 163,144,832 | >= 163,144,832
> 3. W_img3.png
> WildFly_Immediate Dominators for byte [] :
> For Jboss -6
>
> 1. J_img1.png :-
> Jboss6_DominatorTree : as there is no io.netty.buffer.PoolChunk .....
> 2. J_img2.png :-
> Jboss6_Histogram
> 3. J_img3.png :
> Jboss6_Immediate Dominators for byte [] :
>
> Kindly find GC log images for wildFly 11 and jboss 6 .for 15 mnts load run .
> Wildfly 11 ------------ Jboss 6
>
> Total GC :-------- 1167 ------------- 174
> Total GC Time :-------- >21 sec ------------- 6 sec
> Total Reclaimed Bytes :------ 3.32 tb ------------ 480 gb
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9835) Performance issues in WildFly11 as my 90% for jmeter run gets increased to 2x for same set of run as it was in Jboss.
by nilesh ratta (JIRA)
[ https://issues.jboss.org/browse/WFLY-9835?page=com.atlassian.jira.plugin.... ]
nilesh ratta updated WFLY-9835:
-------------------------------
Component/s: JMS
> Performance issues in WildFly11 as my 90% for jmeter run gets increased to 2x for same set of run as it was in Jboss.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9835
> URL: https://issues.jboss.org/browse/WFLY-9835
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Server
> Reporter: nilesh ratta
> Assignee: Jason Greene
> Attachments: J-img3.png, J_img1.png, J_img2.png, Jboss_GClog.png, W_img1.png, W_img2.png, W_img3.png, WildFly11_GCLog.png
>
>
> I have upgraded my application from Jboss6 with java 6 to WildFly11 with java 8 in dev environment.
> Note :
> I am facing some performance issues in WildFly11 as my 90% gets increased for same set of run as it was in Jboss.
> *And minor GC gets increased to 7 times as it was in jboss.*
> And there is no application level code changes in wildfly11.
> *Please find attached files for GC log and Heap dump related inputs.*
> Inputs :
> JVM parameters : Parallel GC with 4 threads , -Xmx6144m Xmx6144m -XX:NewRatio=1 -XX:ParallelGCThreads=4 -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=1024m
> Parameters are same in Jboss 6 and WildFly11.
> Jmeter result overview for 100 users in 15 mnts with 250 sec rampup time.
> As all of our app server is on AWS with same configuration.
> 1. Jboss 6 results :
> Label Count Average 90%_line Min Max Error% ThroughPut
> TOTAL 48664 167 418 0 30374 0 53.80
> 2. WildFLy11 results :
> Label Count Average 90%_line Min Max Error% ThroughPut
> TOTAL 54775 287 887 0 14286 0 60.672
> Note : As my count nd throughput increases but my* 90% is > 2x * for WildFly11.
> Kindly find the attached files for Heap dump as follows with following names in .png format:-
> For WildFly 11 :
> 1. W_img1.png :-
> WildFly11_DominatorTree : io.netty.buffer.PoolChunk ?????
> 2. W_img2.png
> WildFly_Histogram : Class Name| Objects | Shallow Heap | Retained Heap
> byte[] | 53,925 | 163,144,832 | >= 163,144,832
> 3. W_img3.png
> WildFly_Immediate Dominators for byte [] :
> For Jboss -6
>
> 1. J_img1.png :-
> Jboss6_DominatorTree : as there is no io.netty.buffer.PoolChunk .....
> 2. J_img2.png :-
> Jboss6_Histogram
> 3. J_img3.png :
> Jboss6_Immediate Dominators for byte [] :
>
> Kindly find GC log images for wildFly 11 and jboss 6 .for 15 mnts load run .
> Wildfly 11 Jboss 6
>
> Total GC 1162 174
> Total GC Time >21 sec 6 sec
> Total Reclaimed Bytes 3.32 tb 480 gb
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBJCA-1366) [GSS](7.1.z) Need handle failover for end of DB in HA-Datasource Failover
by Bartosz Spyrko-Śmietanko (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1366?page=com.atlassian.jira.plugin... ]
Bartosz Spyrko-Śmietanko moved JBEAP-14242 to JBJCA-1366:
---------------------------------------------------------
Project: IronJacamar (was: JBoss Enterprise Application Platform)
Key: JBJCA-1366 (was: JBEAP-14242)
Workflow: classic default workflow (was: CDW with loose statuses v1)
Component/s: JDBC
(was: JCA)
Affects Version/s: (was: 7.1.0.GA)
> [GSS](7.1.z) Need handle failover for end of DB in HA-Datasource Failover
> -------------------------------------------------------------------------
>
> Key: JBJCA-1366
> URL: https://issues.jboss.org/browse/JBJCA-1366
> Project: IronJacamar
> Issue Type: Enhancement
> Components: JDBC
> Reporter: Bartosz Spyrko-Śmietanko
> Assignee: Bartosz Spyrko-Śmietanko
>
> If configure below, DB3 does not work failover to DB1.
> {noformat}
> <connection-url>DB1|DB2|DB3</connection-url>
> <url-delimiter>|</url-delimiter>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months