Posted Mon, 24 Jun 2019 16:03:53 GMT by

Hi,

We're in the process of upgrading from version 10.4.2.1 to version 11.1.30.3.
The server we've installed version 11 on is identical to our old server, and we're running the agents on the same machines as the old agents.

We are experiencing that pretty much everyting about version 11 is a lot slower than on version 10. The task builder becomes unresponsive for a second or two now and then, and the general feeling of the UI is that it's input lagging (windows closing 0.2 seconds after pressing the close button, etc..).

But also the triggering of workflows takes up to 10 seconds more than the same trigger/workflow on version 10.
Also, the performance of the agents is a lot slower. They not only take longer to actually start, but for some very large workflows they will take almost 2 times as long to finish.

We've looked at the server performance, and the execution server sometime take up to 20% CPU, and i've never seen execution server peak more than about 7% CPU on version 10.

How can we move forward to identify what the issue is here?

Posted Wed, 26 Jun 2019 03:28:50 GMT by

Hello Andreas,

Is it possible to give us the machine specs for the agent and server machines? Is the server that hosts the execution and management servers a dedicated server?

Here are the minimum requirements for installing the software, just want to be sure we are at least at these specs:

https://static.helpsystems.com/automate/help/ame_11/Default.htm#Installation/System_Requirements.htm%3FTocPath%3DWelcome%7CInstallation%7C_____1

 

Posted Wed, 26 Jun 2019 13:45:58 GMT by

Hi,

The server is running on an Intel Xeon E5-2670 @ 2.6Ghz. It's got 16GB ram, and the system disk has got 45GB free space on it.

The server is only hosting the execution and management server.

We came across a workflow yesterday that used to take 30 minutes to perform, that now took 4.5 hours. Please advise.

Posted Mon, 01 Jul 2019 16:45:21 GMT by

Hello?

Posted Tue, 02 Jul 2019 01:00:00 GMT by

Hi Andreas,

Would it be possible to set-up a remote support session where we can take a closer look at this issue? If this is possible please send an email over to AutoMate.Support@helpsystems.com with a list of your availability. In the email, also please verify the Operating System of the machine in question and it's bit level, as well as the version and bit level of the AutoMate software.
Note: Please reference this forum thread in your email.

Posted Wed, 11 Dec 2019 11:40:09 GMT by

Andreas and Justin, this echos our experience also.  I haven't seen runtime slowdowns as exaggerated as what Andreas reported, but we're definitely seeing v11 running at about half the speed of v10 on a similarly-provisioned server. We also have a difference in operating system between our two servers (Win2012 vs Win2016), so that could be an additional factor.

Regardless of specifics, performance is so much worse with v11 that I recommend that you folks update the minimum/recommended system configurations.

Posted Tue, 17 Dec 2019 04:16:00 GMT by

Hello John,

Thank you for the information. We are currently evaluating the situation and will take your suggestions into consideration.

Posted Fri, 21 Jan 2022 09:47:43 GMT by Tamás Hessz ARCONIC-KOFEM LLC Manager
Hi,
We have just recently upgraded from AutoMate version 10 to version 11.6 and we also experience a serious performance degradation when exporting data to Excel. A task that completed in 30 seconds or so in version 10 now runs for about 0.5 hours. We have a task that runs 5 hours (!!) when exporting the data. We have not experienced these anomalies in v.10.
We have an open ticket about this (CAS-0010289777)
Also, years ago when we had version 10 a Helpsystems technician advised us to change a registry entry to switch the debug mode on and off to improve performance and it did help. Does this tweak exists in v.11.6 as well?
Thank you.
Tamas
Posted Tue, 14 Jun 2022 23:58:46 GMT by Devin Cannon
Just to follow-up here.  A bug was logged with our development team for this specific issue.  The bug number was AM-15917.

You must be signed in to post in this forum.