portal entry

select a category, or use search below
(searches all categories and all time range)
Title:

Performance Monitoring Toolset – Auto Connector Tuning

| View in Portal
July 12, 2018 12:00:41 PM GMT
2 Comments
<p>Connector tuning is one of the essential part of setting ColdFusion Server for production deployment. Incorrect values lead to Service Unavailable or Server too busy errors. With ColdFusion 2018 release, most of these assumptions can we verified with actual data. With auto connector tuning, Realtime traffic and load data on the connector will be tracked and displayed on Performance Monitoring Toolset. Admin/developers can log into the Performance Monitoring Toolset to visualize the load on individual site/connector on a time series […]</p>
<p>The post <a rel="nofollow" href="https://coldfusion.adobe.com/2018/07/connector-tuning/">Performance Monitoring Toolset – Auto Connector Tuning</a> appeared first on <a rel="nofollow" href="https://coldfusion.adobe.com">ColdFusion</a>.</p>
Labels: Adobe ColdFusion 2018, Blog, Connector Auto Tuning, Performance Monitoring Toolset, Tuning, Uncategorized

Comments:

I have a few questions after reading this. 1) Does the next to last sentence mean that this whole "auto-connector tuning" feature does not apply to Apache? but only to IIS? It seems that the tuning is only done to the connection_pool_size, yet that sentence about Apache says, "Hence, we are not tuning the connection pool size." I just want to make sure I'm interpreting that correctly. 2) Also, this article doesn't make clear: does the auto tuning really change the values on the fly? No restart of IIS required? Nor of the app pool for the site using the connector? 3) And if the auto-tuning raises the values of one or more connection_pool_size values in one or more connectors, does it then also auto-tune (change) the maxthreads value for the AJP connector XML element in the server.xml file? This document comments (in discussing ratios) how that value "should be the cumulative sum of connection_pool_size[s]", but it never mentions whether the tool changes that value as it autotunes the pool size(s).
Comment by Charlie Arehart
1180 | July 17, 2018 03:37:24 AM GMT
Thanks Charlie for bringing up few points that were missed in the blog. I have updated the post with points asked by you, so that we have entire information updated at one place. Below are the answers for the questions: 1) Does the next to last sentence mean that this whole “auto-connector tuning” feature does not apply to Apache? but only to IIS? Ans: Yes auto-tuning feature is only applicable for IIS and not for Apache, in case of Apache we are just displaying the busy connections. 2)Does the auto tuning really change the values on the fly? No restart of IIS required? Nor of the app pool for the site using the connector? Ans: When auto-tuning happens the pool-size would be increased automatically and there is no need of IIS restart. 3) Does it then also auto-tune (change) the maxthreads value for the AJP connector XML element in the server.xml Ans: While configuring connectors, if the sum of pool size of all the sites configured is above 500, then user has to manually increase the maxThreads property of the AJP connector in the server.xml. During auto-tuning we only auto-tune the pool size at IIS connector level. In CF server there is a property maxThreads which doesn’t get auto-tuned. There is a queue at ColdFusion server level, which queues the request if there are no worker threads available. But there is no such queue at mod_jk connector level.
1176 | July 18, 2018 07:58:15 AM GMT