ACS = world’s first ColdFusion consultancy? ~40 of us in the field as an extension of engineering team. “PE” (performance engineering services) are our flagship offering (founded in 2001). PE = a continuation of ACS offerings. Note about this talk: This webinar is a variation on a talk we originally delivered at the ColdFusion Summit in Las Vegas in Oct. 2014.
Apologies to Steve Jobs, but… ...biggest news from Webapper of late is our formal moved into managed services cloud hosting. Still finalizing w/ HOSTING. Coming soon! More on this later in the presentation.
But, if you’re a HOSTING customer, you get us automatically! We’re the exclusive ColdFusion platform support partner for all HOSTING customers.
We’ve seen a lot of ColdFusion. We know it’s incredibly fast and stable, when you do things the right way.
Our TNT work is very empirical - we typically look at ~5 different data sets when tuning/troubleshooting a server. We don’t just apply generic settings every time. The settings end up being similar, often, but always based on app- and server-specific data. Today, however, we’ll try to share some good general settings, averaged over hundreds of engagements and thousands of ColdFusion servers.
-Xms4096m -Xmx4096m - This increases the overall heap size to 6GB and added a start size of the same size.
-XX:NewRatio=4 -XX:SurvivorRatio=8 - These are added to increase the size of the Young Generation and to relate its size to the overall heap, which will help to reduce the number of shortlived objects getting move to the Old/Tenured generation too soon. -XX:+UseCompressedOops - This relates directly to Java running on 64 bit systems. -Xss256k - This resizes the default thread size down to 256k per thread which is typically more efficient in our experience. -XX:+CMSClassUnloadingEnabled - Use this if you see this entry in your logs, as it indicates suboptimal performance of your existing settings: "Please use CMSClassUnloadingEnabled in place of CMSPermGenSweepingEnabled in the future." -XX:+UseParNewGC - This changes the Young Generation collector to one more suited to work with the CMS collector.
-XX:+DisableExplicitGC - This will prevent any unnecessary Full GC's from occurring. -XX:+CMSScavengeBeforeRemark -XX:CMSInitiatingOccupancyFraction=68 -XX:CMSFullGCsBeforeCompaction=1 - These are all enhancements used over the past 2-3 years by our team for 64-bit systems and developed from a lot of analysis and load testing. XX:+UseCMSInitiatingOccupancyOnly and XX:CMSInitiatingOccupancyFraction=68 are typically used together and are used to start the concurrent collection earlier; in this case the collection will start when the Old/Tenured’s heap size reaches 68% used. This should reduce the number of Full GC's. -XX:+CMSScavengeBeforeRemark will force a collection of the New/Young space prior to a CMS remark as this should reduce its size and thereby the time spent in remark.
-XX:+UseConcMarkSweepGC - This changed the garbage collector from the parallel collector to concurrent mark sweep or CMS collector which is better for 64-bit systems. -XX:PermSize=192m -XX:MaxPermSize=256m - The permanent generation is where ColdFusion stores its classes; we often observe that this space is getting used up quickly, so we add a start size and increase maximum size also.
At Webapper, we have a service that we call The ColdFusion TNT which stands for Tuning and Troubleshooting… and we have a 55-point checklist where we check various settings in the operating system, in the web server and the application server These are primarily checks for performance and security For example, we check what ports are open via nmap, and also simple things like hard drive free space We once had a server go down and we were checking different things, we were pinging it, memory was ok, we can RDP into it and we were checking if the CF and webserver services were up, so what’s going on? it turns out that there’s no more drive space! (Nasty performance bottleneck!) For IIS, we check things like compression and application pool recycling settings Also comb through CF Admin optimizations
Thread optimization is a crucial performance aspect of your servers.
To optimize thread settings, there are 3 areas that all work together, 3 areas or POOLS, and are controlled by different things.
First is tomcat’s server xml file…
this is located under each of your instance’s /runtime/conf directory… so if you have an instance called instance01, it would be under C:\ColdFusion10\instance01\runtime\conf\
this is the tomcat thread pool allotment for the web connector…
there’s also an executor maxthreads setting, and we also set that to the same one, but not for the internal webserver, but for the catalina executor
this is the workers.properties file, which controls the thread pool for IIS.
This is specific to a web connection…
but this file is under the C:\ColdFusion10\config\wsconfig directory then you would see multiple numbered directories under there, depending on how many websites you have connected to ColdFusion
All these settings are referenced in that adobe blogpost
This is CFAdmin’s thread settings, located under Server Settings > Request Tuning.
The way we do it, we can run load tests against the application and optimize and tune these settings,
or we analyze thread metrics whether via metrics logging, SeeFusion DB logging or FusionReactor logging, but we analyze the threads and for example if we see that the max you can get is 50 and you have thread starvation, we raise that limit.
Or if we see that you are already at 250, and your max is 110, then we lower that to 125, just so that we can put those resources back into the stack
but if you don’t have that luxury, just raise the defaults by a factor of 5 or 10
So with the server.xml file, I’ve seen maxThreads where if you change it, it changes the setting in CFAdmin too.
it’s also known as the wsconfig tool… who uses the web server connector…
that’s great… most people during installation would just configure ALL sites to use CF, please don’t do that. Use the webconnector post-installation of ColdFusion
one rule of thumb, please run it as ADMINISTRATOR, even if you are logged in as Administrator
if you are using multiple instances, you HAVE to use the individual directory’s connector
also if you are using clustered instances, you use the webconnector to connect to whatever instance or cluster you want
I mentioned that during installation of CF, to not configure the webserver but to use the connector after installation.
When you do use it, do not use ALL…
do create connections for each website, just so that you have different connector pool settings,
but you do have to aggregate those swimming pool settings into the server.xml…
Here’s a PROTIP… For trouble shooting why CF is not working with your webserver (IIS, Apache), do this...
just click on ADVANCED here and enable VERBOSE LOGGING and you can also set some thread settings there
so now I turn you over back to the everlovable future President of the US 2024, PAT QUINN
Automatically optimized: We of course would create a "gold image" ColdFusion server, with our "Webapper Way" tuning optimizations, and use that as the starting point for new hosting setups. Automatically load-balanced: In other words, your app/site/stuff automatically runs on multiple servers, and is load balanced. Automatically redundant: This is the cloud era's version of backups, but, it can and should be smarter, like taking full images as backups, and also making sure any storage media/drives are always redundant, too. Automatically monitored: A hosting system should be monitoring key metrics, and should auto-failover (using the backups and other redundancies) if problems arise. Automatic data tier clustering: There's a database services partner to help with/manage this piece.
All of this will be delivered as virtual servers running on top of HOSTING.com’s cloud platform. Our goal is for this to be “point and click easy” to purchase and use.
Want to learn more? Let’s talk next steps.
Tuning the Performance of Your ColdFusion Environment to Racecar Specs!
Tuning the Performance of
Your ColdFusion Environment
to Racecar Specs!
• This webinar is being recorded and an on-demand
version will be available at the same URL at the
conclusion of the webinar
• Please submit questions via the button on the upper
left of your viewing panel
• If we don’t get to your question during the webinar,
we will follow up with you via email
• View related resources via the “Attachments”
button in your viewing panel
• On Twitter? Join the conversation: #ColdFusion,
We are Webapper
• Co-founded in 2001 by two former
members of Allaire Consulting
• Speakers today:
• Patrick Quinn: Co-Founder, CTO of
• Mike McCracken: Director, Professional
Services for HOSTING
Recommended Thread Settings
(Notes: connection_pool_timeout is in seconds;
must be the same as server.xml's connectionTimeout)
New SOTA ColdFusion Cloud Hosting
• Automatically optimized
• Automatically load-balanced
• Automatically redundant
• Automatically monitored
• Automatic data tier clustering
• via Twitter: @IamSigmund
• via Email: firstname.lastname@example.org
• HOSTING.com Customers:
Michael McCracken | HOSTING Director, Professional Services
Patrick Quinn | Webapper President and CTO
For more information about solutions from HOSTING and Webapper,
please contact us at +1 888 894 4678.