Skip to main content
Solved

Excel Advanced is very slow on a particular VM

  • October 22, 2024
  • 8 replies
  • 109 views

Forum|alt.badge.img+11

Hi everyone,

 

I have noticed a strange problem with the Excel Advanced package.

Usually reading an Excel File is quite fast with Automation Anywhere. I am using the Excel Advanced : get function.

I have a virtual machine for the PROD environment and another one for the TEST environment. On the TEST environment, it is particularly slow, it takes roughly half a second to a full second to get the value of a single cell. However, on the PROD environment it is still very fast. I have no explanation for that.

I have compared and the Automation Anywhere package versions are the same. The version of Excel is in both cases the same (Microsoft® Excel® for Microsoft 365 MSO (Version 2408 Build 16.0.17928.20114) 64-bit). Both have the same RAM amount, same CPU...

The only difference is that I am connected to Excel through a Microsoft Account different for the PROD and TEST env (typically username-prod@contoso.com vs username-test@contoso.com )

Has anyone ever faced the same problem ?

 

 

Best answer by Augustin

My problem seems to have been solved by upgrading the package Excel Advanced to the latest version of the bot (It had been developed some time ago, and it was the 2021 version of the package)

View original
Did this topic help answer your question?
This topic has been closed for comments

Oli.Morris
Automation Anywhere Team
Forum|alt.badge.img+10
  • Automation Anywhere Team
  • October 22, 2024

It may be worth checking what percentage of RAM and CPU are being consumed at the time of execution. Dev machines, by their nature, will have lots of background processes running which will likely affect the execution.

In these situations I also ensure that any delays I’ve implemented in the bot can be controlled via by config file i.e. longer delays for DEV/UAT and shorter ones in PROD.


Forum|alt.badge.img+11
  • Navigator | Tier 3
  • October 22, 2024
OliverM108256 wrote:

It may be worth checking what percentage of RAM and CPU are being consumed at the time of execution. Dev machines, by their nature, will have lots of background processes running which will likely affect the execution.

In these situations I also ensure that any delays I’ve implemented in the bot can be controlled via by config file i.e. longer delays for DEV/UAT and shorter ones in PROD.

I have checked that and the RAM use is well below 100 %


Dineshkumar Muthu
Flight Specialist | Tier 4
Forum|alt.badge.img+9

Hi @Augustin 

Verify if the location of the Excel file (local vs. network drive) is the same in both environments. Accessing files over a network can sometimes be slower than accessing them locally.


Forum|alt.badge.img+11
  • Navigator | Tier 3
  • October 22, 2024
DK 964 wrote:

Hi @Augustin 

Verify if the location of the Excel file (local vs. network drive) is the same in both environments. Accessing files over a network can sometimes be slower than accessing them locally.

In both environments it is a local file in the downloads folder, given the fact I have also developed the bot that downloads this Excel file


Dineshkumar Muthu
Flight Specialist | Tier 4
Forum|alt.badge.img+9

Hi @Augustin,

does this excel file has any formula or scripts? also tell me more about the file.


Dineshkumar Muthu
Flight Specialist | Tier 4
Forum|alt.badge.img+9

@Augustin, you can try to execute the same bot to the different VM. if you are not facing any problem in different VM then there might be some issue with that specific VM.


Forum|alt.badge.img+11
  • Navigator | Tier 3
  • October 22, 2024
DK 964 wrote:

@Augustin, you can try to execute the same bot to the different VM. if you are not facing any problem in different VM then there might be some issue with that specific VM.

That is exactly what I explain in my first post.

Sorry if I was not easy to understand, English is not my mother tongue


Forum|alt.badge.img+11
  • Navigator | Tier 3
  • February 24, 2025

My problem seems to have been solved by upgrading the package Excel Advanced to the latest version of the bot (It had been developed some time ago, and it was the 2021 version of the package)


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings