Control Charts running slowly in JMP 18

[#1]

I have recently been upgraded to JMP 18.2.1. I use Levey Jennings Control Charts very often in my job. While using JMP 17, I had been developing a script that takes a Stacked table from our database and uses the By() function to plot control charts of X(Batch) and Y(Result) for each unique Component in the Component column (By(Component)). 

Since upgrading to JMP 18, I have found this functionality runs very slowly, but specifically when using the new Control Chart launcher. If I use the Legacy Control Charts, the charting is much faster. The total runtime is proportional to the total size of the stacked table and the number of unique analysis. This difference in speed appears to have nothing to do with my script, as I see similar slow charting times even when using the Analyze > Quality and Process > (Legacy) Control Charts > Level Jennings launch windows. What takes just 2-3 seconds using legacy control charts can easily take >45 seconds for me using the same chart options and the same data table in the CCB platform. If I do this in JMP 17, it is much faster. Is anyone else seeing this kind of issue? Any way to fix this? It is crippling my ability to write really useful scripts that can help our engineering team quickly access and review data.

These are the exact options I am using for the Legacy Control Charts Levey Jennings window.

And these are the options I am using in the Control Charts Levey Jennings window.

Plotting charts from the table I currently have open took 3 seconds on the legacy platform and >50 seconds on the CCB platform, just as an example.

[#2]

Are you sure you are creating same plots as you are using subgroup instead of label?

[#3]

I have done it both ways (Subgroup vs Label) and they both take significantly longer than the Legacy Control Charts. I didn't time them, but off of feel alone, Label was maybe 20% faster. It was still very slow.

[#4]

You might want to contact JMP support, especially as it is slow when running it from JMP and not using script (with script there could possibly be some speedups which could be done).