A new algorithm has been introduced to increase the stability of the bots during playback. The limiting factor is a hard limit in the SAP GUI Script API whereby if the SAP GUI windows use up more than 1Gb of RAM, then this causes the bots to become unstable. For playbacks, this could cause the bots to become unresponsive or simply crash which resulted in technical errors and current scripts failing.
Previous Method
The previous method available from version 2.20 of Testimony saw SAP GUI dialog sessions being distributed based upon the number of SAP GUI windows that were open. The bot with the least number of SAP GUI windows open would be selected to run the next user session. However, we now know that memory is the limiting factor (not number of windows).
New Method
The allocation of a new SAP GUI logon session is now determined dynamically by selecting the bot with the lowest memory consumption.
Impact
There is now a full understanding that each bot can have a maximum memory utilization of between 1.0Gb and 1.1Gb. This is a hard limit within the SAP GUI scripting API. If the bot goes above this, then it either becomes unresponsive or completely crashes. This new technique of selecting the bot with the least amount of memory consumption will ensure the bots remain as stable as possible during the playback processing.
Bot memory consumption is now available
Post your comment on this topic.