Same UI Path project, different results on different computers

Help Studio
1

My coworker wrote a UI Path sequence to open a large Excel file, and then create a new Excel file with some calculated results.

This project runs in under 20 minutes on my coworkers laptop.

This project, when it runs, takes almost 2 hours on my desktop. My desktop is an 11gen i5 processor and I have 64G of memory. While the sequence is running, the only odd thing I notice is that in Task Manager, Studio and Studio and UI Path Executor (32 bit) both run RED in the power consumption and combined they occupy about 1/3 of my memory. Over the weekend, I even did a complete wipe and reinstall of Windows 10, all updates/patches applied, drivers up to date and HP scans show fully operational.

What could cause this sort of behavior?

I say “when it runs” because the sequence doesn’t always function. Sometimes Studio simply shows Not Responding or the program runs for 5 hours before I terminate it. One time I did receive an error and only 1 time. I did mention this is a fairly large data set.

21.10.3+Branch.master.Sha.8291b2799a85589c5b075e0d1f69016fc83eec97

Could not retrieve the result of the job execution. This might be because a message was too large to process.

RemoteException wrapping System.Exception: Could not retrieve the result of the job execution. This might be because a message was too large to process.

I edited the Excel file to a fraction of the size and there is no improvement in the performance of the sequence.

2

Just in case, are you executing in Debug mode?

3

Before I ran in Run mode, I removed 16 unused columns form the Excel file and now the file is small.

The sequence was successful when taken out of Debug mode. UI Path Executor 32 bit is still running Very High on the power consumption.

4

Is one computer working locally on the company network and the other across VPN? Does the desktop have anything else running that’s not running on the laptop?

This isn’t going to be a UiPath issue. This is a system, network, and resources issue.

5

The files are all local, running on an SSD