Data Infrastructure Management Software Discussions
We encounter slow workflow execution on our new WFA server (WFA 4.2 RC1).
The Create Volume command took 36219 milliseconds (>35 secs) to complete. I am using a local user account with CRL (Certificate Revocation List)
On the old WFA server (WFA 4.1), same command took 10344 milliseconds (>10 secs) to complete.
Any suggestions appreciate.
See The Solution
I meant to say that CRL is disabled for local user.
We noticed the same thing as well when we were testing out 4.2RC1. We then tried to start the services with a domain user and it went super fast.
Can you test out that scenario as well to confirm?
Please try this
set timeout value to 1 sec.
Got 404 on the link
above link is working fine
missed last bracket
we have started the services under a domain user. The workflow execution is still very slow.....
Hi Henk Snel,
Please provide your machine configuration.
So that we will try to reproduce it locally
This is the machine configuration:
CPU: Dual 2.50 Ghz Intel Xeon
OS version: Windows 2012 R2
System Type: Server (VMguest)
I've found the problem.
The problem is the slow loading of Powershell DataONTAp module within WFA. Which is 4.3.0.
I've replaced that version by 4.2.0 (which comes with WFA 4.1).
The volume create command now takes 10 secs to complete in stead of 40 secs.
We will try to reproduce this issue. and i will raise a bug for the same.
WFA 4.2 (GA) has been released.
The workflow execution is still terrible slow with DataONTAp 4.5.0 vs DataONTAP 4.4.0.
The creation of a vserver takes more than 40 secs with DataONTAP 4.5.0. Whereas with DataONTAP 4.4.0 it takes approx 8 secs.
I’ve executed the following test scenario:
This test was executed with WFA 4.2 and DataONTAP toolkit 4.5.0.
View solution in original post
Can you please post more detail for what you mean by / did for steps 1, 2, 3, & 7?