Performance problems after upgrading from 4.0.4 to 4.1.4

Bug reports.
gcushman
Posts: 10
Joined: Fri Dec 27, 2013 8:16 pm

Performance problems after upgrading from 4.0.4 to 4.1.4

Post by gcushman » Fri Dec 27, 2013 8:48 pm

I've reproduced this issue on Windows 7 (x86) and 2008 R2 using both Ranorex Studio and TestSuite Runner.
I have simple C# code that checks for existence of a button on a dialog box. Here's the code with a bunch of debug log statements added:

Code: Select all

Report.Debug("Checkpoint A");
Report.Log(ReportLevel.Info, "Waiting a total of: " + repo.ScribeWorkbench.ScribeWorkbenchDialogTextStrings.SaveChangesTextInfo.SearchTimeout + "  for the Save changes dialog.  Contact Automation Team if timeout needs to be increased.");
Report.Log(ReportLevel.Info, "Waiting a total of: " + repo.ScribeWorkbench.ScribeWorkbenchDialogTextStrings.SearchTimeout + "  for the ScribeWorkbenchDialogTextStrings object.  Contact Automation Team if timeout needs to be increased.");
Report.Log(ReportLevel.Info, "Waiting a total of: " + repo.ScribeWorkbench.SearchTimeout + "  for the ScribeWorkbench object.  Contact Automation Team if timeout needs to be increased.");
Report.Debug("Checkpoint B");
if (repo.ScribeWorkbench.ScribeWorkbenchDialogTextStrings.SaveChangesTextInfo.Exists())
{
	Report.Debug("Checkpoint C");
	Report.Log(ReportLevel.Info, "The Save changes dialog appeared, clicking No.");
	Report.Debug("Checkpoint D");
	repo.ScribeWorkbench.No.Click();
	Report.Debug("Checkpoint E");
}
else 
{
	Report.Debug("Checkpoint F");
	Report.Log(ReportLevel.Debug, "The Save changes dialog did not appear.");
	Report.Debug("Checkpoint G");
}
In 4.0.x (tried 4.0.4 and 4.0.6), when the object in the IF clause (SaveChangesTextInfo) does not exist, the time for the script to move from "Checkpoint B" to "Checkpoint F" is about 5-6 seconds.
In 4.1.4 (and 4.1.0) running the same exact code, the time between the 2 points is 65-66 seconds. I attached screenshots of log output for each case.

4.0.x log output:
Ranorex Upgrade Issue 4.0.4.png
4.0.x log output:
Ranorex Upgrade Issue 4.0.4.png (14.4 KiB) Viewed 928 times
4.1.x log output:
Ranorex Upgrade Issue 4.1.x.png
4.1.x log output:
Ranorex Upgrade Issue 4.1.x.png (14.38 KiB) Viewed 928 times
Any idea if this is a known problem?

Thanks
Greg

User avatar
mebner
Posts: 61
Joined: Tue Dec 17, 2013 6:42 pm

Re: Performance problems after upgrading from 4.0.4 to 4.1.4

Post by mebner » Fri Jan 03, 2014 1:41 pm

Hi Greg,

We will analyze the issue and get back to you as soon as possible!

Regards,
Markus

User avatar
mebner
Posts: 61
Joined: Tue Dec 17, 2013 6:42 pm

Re: Performance problems after upgrading from 4.0.4 to 4.1.4

Post by mebner » Tue Jan 07, 2014 5:43 pm

Hi Greg,

We analyzed the issue!
There is a bug in 4.0.X which causes Ranorex to use the search timeout of the app folder instead of the effective timeout of the repository item when the app folder's use cache property is set to true.
This bug was fixed with 4.1 which is the reason why the timeout is different to 4.0.X.
The right(same) timeout will be used when you set the use cache property of the app folder to false (in 4.0.X and 4.1.X).

Regards,
Markus

gcushman
Posts: 10
Joined: Fri Dec 27, 2013 8:16 pm

Re: Performance problems after upgrading from 4.0.4 to 4.1.4

Post by gcushman » Wed Jan 08, 2014 1:30 pm

Thanks for the reply! I will upgrade again and flip that option and retry our testcases.

Regards,
Greg