ColdFusion 8 Performance Brief

I’ve mentioned ColdFusion 8 performance gains previously, and said that we’d publish the complete performance brief with the test specifics and details. That brief is now online.

7 responses to “ColdFusion 8 Performance Brief”

  1. Adam Reynolds Avatar
    Adam Reynolds

    Yeah I noticed they don’t go into structures (structNew() is one of the most used functions).
    I understand this is actually slower.

  2. John Farrar Avatar
    John Farrar

    OK… are all these comparisons the same for Pro as for Enterprise? I am thinking we don'[t have demographics on the load performance for CF Pro.

  3. Jason Delmore Avatar
    Jason Delmore

    StructNew() falls under the general "ColdFusion Structures" line on page 2 and is ~1.9 times faster in CF8 versus 7 or 6.1. 🙂

  4. Dan Roberts Avatar
    Dan Roberts

    I looked into report creation performance and reviewed the CF7 performance brief. I don’t see a similar section in the CF8 performance brief. The CF7 brief recommends 3-5 concurrent requests. Has there been any increase in performance in this area? We plan on moving to CF8 right away but trying to make some development decisions based on performance. Thanks

  5. Manjukiran Avatar

    Hello Dan,
    In CF7 performance brief, the area "Report Creation" was used as an example to show the perf differences between CF7 Std and CF7 Ent editions. If you look at the graph, CF7 Std can process 3-5 concurrent requests where-as CF7 Ent can process 10-11 concurrent requests for the same number of VUs.
    However in CF8 performance brief, PDF document generation was chosen as an area to show the perf differences between CF8 Std and CF8 Ent editions.

  6. Alex Hubner Avatar
    Alex Hubner

    Page 10 says that under ColdFusion Server Settings, the "Max Number of Jrun threads" for CF8 was set to 50 while older versions (6/7) were configured with only 20. Why?

  7. Tom Jordahl Avatar
    Tom Jordahl

    We upped the number of JRun threads because:
    1. Machines are faster
    2. Enterprise edition has the request limits now and we need JRun to let the request get to these throttles
    3. 20 was too low (see #1 & #2)

Leave a Reply