18 January 2026:
Sahi Pro is an enterprise grade test automation platform which can automate web, mobile, API, windows and java based applications and SAP.
This forum is now archived and is in read-only mode. Please continue discussions on our improved new Sahi Pro Community forum.
Sahi Pro is an enterprise grade test automation platform which can automate web, mobile, API, windows and java based applications and SAP.
Sahi's Performance issues (Older Version without Rhino)
pankaj.nith
Members
Hi,
I am using an older version of sahi (quite old) that has been tweaked a wee-bit to cater to our needs. For this reason we have to use the older version but at times start facing performance issues when the script length increases considerably. Anything above 1000 execution steps will leave sahi dead stuck on every other step. Other scenarios which add up to the sluggish response are too many variables being used, too many iterations, too many steps, too many regular expressions etc (which are to some extent in the hands of the coder). I just happened to check the memory usage of firefox (the browser that I use) and it showed above 530Mb and processor usage fluctuating between 50-99%. Java.exe was also using above 22Mb. I hope these things must have been addressed to a great extent in the latest build of sahi as alot of script execution has been taken off from the browser (I am not able to check it much as got stuck using the new build).
Any suggestions to make my scripts perform better on older sahi will be a great help. It takes almost a day to run scripts having 3000-5000 lines of code defying the entire purpose of automation.
Thanks and Regards,
Pankaj.
I am using an older version of sahi (quite old) that has been tweaked a wee-bit to cater to our needs. For this reason we have to use the older version but at times start facing performance issues when the script length increases considerably. Anything above 1000 execution steps will leave sahi dead stuck on every other step. Other scenarios which add up to the sluggish response are too many variables being used, too many iterations, too many steps, too many regular expressions etc (which are to some extent in the hands of the coder). I just happened to check the memory usage of firefox (the browser that I use) and it showed above 530Mb and processor usage fluctuating between 50-99%. Java.exe was also using above 22Mb. I hope these things must have been addressed to a great extent in the latest build of sahi as alot of script execution has been taken off from the browser (I am not able to check it much as got stuck using the new build).
Any suggestions to make my scripts perform better on older sahi will be a great help. It takes almost a day to run scripts having 3000-5000 lines of code defying the entire purpose of automation.
Thanks and Regards,
Pankaj.
Comments
Tinchie8: Do you mean your problems got fixed with the new build?
We are using an older version of sahi that was tweaked by our dev guys (added a few APIs) to suit our product. I dont think it would be much difficult to move to new sahi provided the iframe related issue (that i have talked about in another thread) gets addressed.
Regards,
Pankaj.