Coldfusion 10 slower when using Java 1.7 compared to 1.6

Question

I have a webservice running on Coldfusion 10 64bit. While investigating a memory leak I went to upgrade the JRE from 1.6 to 1.7 but noticed a significant performance hit. I had created a simple test webservice which on JRE 1.6 I could run easily at 5000 requests per minute as soon as I changed the JRE to 1.7 though this rate drops too 2000 or less per minute. Does anyone know of tuning settings or something I am missing.

The preference is to use JRE 1.7 as it appears to have fixed the memory leak issue I was having.

Running Server JRE: java version "1.7.0_51" Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
Garbage Collection in JVM settings: -XX:+UseParallelGC
Changed Garbage Collection to : -XX:+UseG1GC this made no difference.

Followed the recommendations from here with no increase in performance. Will review with jvisualvm and post my findings.

Update: Java 7 has changed the way it deals with synchronizing class loaders and it looks like this may be the cause of the slowdown.

Update Adobe has acknowledged the bug and is looking to fix it. Adobe bug base record.

It should say if you do `java -version` from the command line - if CF isn't using the system default you'll need `/path/to/cf/jre/bin/java -version` or similar. Or check the "System Information" page in CF Administrator - looks like you'll want "64-Bit Server VM" in the Java VM Name. — Peter Boughton, Feb 13 '14 at 16:13
What are your JVM settings. In particular which garbage collector are you using? — James A Mohler, Feb 13 '14 at 16:13
Hmm, unless I'm misunderstanding, that's the right one. :/ Something else to investigate is enabling JRockit VM - I've read about that being better performing and integrated into Java 7 in some way, but I'm not sure of specifics. — Peter Boughton, Feb 13 '14 at 16:18
Use **JConsole** or **jvisualvm** to monitor the memory usage. You may have to tune in your jvm as per JRE 1.7 — Anit Kumar, Feb 13 '14 at 23:50

score 5 · Accepted Answer · answered Oct 14 '14 at 21:05

5

Answer for this is that Adobe has acknowledged the bug and is looking to fix it. Adobe bug base record.

answered Oct 14 '14 at 21:05

Alan Bullpitt

456
4
13

Did this ever get fixed? The bug record lists it as a duplicate of another bug, but there's no reference to the duplicate or its status. – user3071284 Aug 27 '15 at 18:34
1

Yes this was fixed in ColdFusion 11 Update 5 and ColdFusion 10 Update 16. – Alan Bullpitt Aug 27 '15 at 19:12

score 1 · Answer 2 · edited Jul 18 '15 at 11:27

I would recommend that you review the JVM Thread Dump data in between your 2 load testing runs (JRE 1.6 vs. JRE 1.7). I have seen CF10 class loader issues in the past associated with the usage of cfdump and cfquery in-memory (query of queries).

Focus your analysis on any thread lock contention problem that you may be facing with JRE 1.7.

The class loader change you are referring to is supposed to actually improve concurrency of the class loading operations but still not impossible that it may trigger some slowness in your environment.

Another recommendation is to look at your GC memory allocation rate. For this purpose, turn on verbose:gc and compare the output data between your 2 runs. Determine if any increase of the GC memory allocation rate and/or GC frequency could be at the root cause of this drop of throughput.

Finally, perform a very close review of the JVM arguments. Ensure that your Java heap tuning arguments, including heap sizing are exactly the same as per JRE 1.6 so we can compare apples vs. apples.

The example I was using for the load test was a stripped down webservice which has no queries or dumps. It creates an object which has 2 properites. 1 is a simple text string and the second property was a array of an object. This second object had one property a string field. This is why I assumed it was due to the concurrency of the class loading operations. The JVM arguments where Identical as it was the same machine just changing the JRE the server was using. I will look at the verbose:gc output later on. — Alan Bullpitt, Apr 11 '14 at 20:22

Coldfusion 10 slower when using Java 1.7 compared to 1.6

2 Answers2

Linked