Open JMP took longer time in JMP18.1 compared to JMP17.2

[#1]

Hello expert,

We have 5 PCs with JMP license - JMP 17.2.

We just upgraded 1 license to JMP 18.1 for software & system testing.

Observed that JMP 18.1 took longer time to open compared to JMP 17.2. The difference is almost 20 secs.

(It's really troublesome because I need to open JMP during meeting with our management & they cannot wait additional 20 secs)

Anyone else having this issue?

Why does it happen? Is it related to default preference?

What can be done to make it fast?

Refer below time taken;

PC 1 (JMP 17.2): 3 - 4 secs

PC 2 (JMP 17.2): 3 - 4 secs

PC 3 (JMP 17.2): 3 -4 secs

PC 4 (JMP 17.2): 3 - 4 secs

PC 5 (JMP 18.1): 22 - 23 secs.

[#2 · Accepted solution]

Could have something to do with the my.jmp.com connection but most likely it shouldn't be that slow. Maybe contact JMP support, they could have some benchmark scripts / files they can send to you or ask to run to see what could be the issue (or if there is even an issue).

[#3]

Thanks @jthi .

Will contact JMP support on this because I may need to downgrade back to 17.2 if nothing can be done.

Not worth to add 20secs.

[#4]

If the information you provided is all you have, then I'd be very suspicious of PC5.  From an experimental point of view, if this happens on only that machine, perhaps it is something about that machine.  At a minimum, can you confirm that PC5 opens JMP 17.2 more quickly? 

Also, while I agree that 20 seconds is too long, and I understand the time sensitivity of executives, "they cannot wait an additional 20 seconds" seems a bit extreme to me.  Couldn't you open JMP before any presentation?

[#5]

Hi @dlehman1 ,

PC5 originally used JMP 17.2 (we didn't experience the long time taken to open JMP before the upgrade).

We started seeing this lag after we upgraded to JMP 18.1.

We also have checked the computer/system requirement, all PCs use the same system requirement.

It may be extreme for you, however, when we perform software & system testing demo to management (which we need to do before we deploy new JMP version across the organization), we need to start with opening the JMP software.

If the 20secs only happen 1-2 times = possible by chance. forgiven

When it happen 3-4 times = there is pattern & it is annoying.

When it happen >5 times = do something about it. open the software presentation is only a containment action but not solving the issue.

Thanks to the suggestion. We will see if we need to downgrade back to JMP 17.2.

[#6]

No need to have collinearities in the DOE.

On many system there should be now installations for JMP 17.2 and JMP 18.0.1.

[#7]

for a fair comparison, you should disable all AddIns.

I made some tests and got for both versions values around 5s when starting JMP via 

"C:\Program Files\JMP\JMP\18\jmp.exe" C:\temp\script.jsl

with the script

//!
caption("stop");

With 50 AddIns activated, it's ~ 11s.

[#8]

Thanks @hogi for the suggestion.

I will check if disabling the add-ins help.

From feedback I received from JMP Technical support, possibly it is due to RDP connection to the terminal/Hyper V.

But, other JMP 17.2 PCs (VM) also using the same systems.