Question
Infosys Ltd
IN
Last activity: 26 Feb 2019 7:46 EST
Bot performance improvement suggestions
Hi,
We have created a RPA bot which interacts with a web application and mainframe application. Bot will first read from the web and then fetch the necessary details from Mainframe and update back the web application with the details.
The web application takes around 10 - 15 seconds to load the full page. But bot takes around 35 - 40 seconds to read the required fields from the page before proceeding to Mainframe. We tried different options mentioned in the below post: https://community1.pega.com/community/pega-support/question/slow-browser-performance
Our studio version is 1087. In the above post there is an updated version mentioned to speed up the performance.
When we did manual interrogation, Bot takes around 35 seconds to match the few required controls. We kept match rules to at max 1 or 2 only.
Is there a way to speed up the matching process? If we upgrade our version to the recent version, will there be any improvements? Any suggestions or ideas to resolve this kind of situations are most welcome
Thanks!
Pegasystems Inc.
US
Matching can be affected based on the hierarchy of the controls. You can further improve match-time by creating a more structured hierarchy.
For example, if there are over 100 button controls under the webpage, it will iterate through all the buttons before finalizing the matching on a button control - this can be slow. So to help with that, you can interrogate a parent tag (like a <div>) above the button, then matching will only iterate and check for buttons under the parent tag. So matching would first find the parent tag (to quantify, iterate 10 controls) then it would match to the button (iterate 3 controls).
So now you're asking... how do I change the hierarchy on my adapter? I have created a basic tutorial on how you can do just that. Attached.
Upgrading can also give you a performance boost depending on what is actually slow... you won't know until you test it.
Pegasystems Inc.
US
Before you change the hierarchy manually, you should try this as well - https://community.pega.com/knowledgebase/documents/working-single-page-web-applications. It has the built in ability to create a hierarchy yourself (added in 8.0.1081). Sometimes it does not work for me though. It depends on the page structure.