Ranorex verses White Performance

Ask general questions here.
atom
Posts: 357
Joined: Sun Dec 07, 2008 11:14 pm
Location: Dublin, Ireland

Ranorex verses White Performance

Post by atom » Tue Apr 10, 2012 5:22 pm

Hiya,

We took a look at the WHITE automation framework (which is basically a wrapper over UI Automation)
We noticed that it is often better performance than Ranorex
We believe this is becauseRanorex duplicates elements in its element tree (one element for pure MSAA and another for UI automation over MSAA)

Therefore we would like to know how to turn off all plugins, to force ranorex to use only UI Automation for everything, and not to use the UI Automation Raw view, but instead the Control view (I think its called)

This way we hope to improve performance, by not applying many interfaces to same object, and reducing the element tree size

Thanks,
Clayton

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: Ranorex verses White Performance

Post by Support Team » Wed Apr 11, 2012 2:10 pm

Hello,
We believe this is because Ranorex duplicates elements in its element tree (one element for pure MSAA and another for UI automation over MSAA)
Usually, we create UIAutomation elements or MSAA elements and not both.
It could be that we are a little bit slower because of additional checks but this should improve the reliability and accuracy.
not to use the UI Automation Raw view, but instead the Control view (I think its called)
This is not possible, you cannot switch between Raw and Control View.

Do you have a specific case where you have seen the described behavior (one element for pure MSAA and another for UI automation over MSAA)?
In general it would be very helpful if we get as much information as possible. This would increase the possibility that we will be able to reproduce the issue/find a solution for the specific problem.

Regards,
Markus
Ranorex Support Team
.
Image

atom
Posts: 357
Joined: Sun Dec 07, 2008 11:14 pm
Location: Dublin, Ireland

Re: Ranorex verses White Performance

Post by atom » Wed Apr 11, 2012 2:23 pm

Hiya,

The difference we see between WHITE and Ranorex is that to find our control of interest the Ranorex element tree is like 10-15 levels deep, and ranorex spy is really slow when it gets to such a level.
WHITE and UI Spy (Microsoft) are very quick, as the control to them is visible 3-4 levels deep

We also see a bug performance different on TABLE elements, WHITE and UI Spy alot quicker than Ranorex

Cheers
Clayton

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: Ranorex verses White Performance

Post by Support Team » Wed Apr 11, 2012 8:54 pm

atom wrote:anorex element tree is like 10-15 levels deep ... WHITE and UI Spy (Microsoft) are very quick, as the control to them is visible 3-4 levels deep
If the number of elements is different (raw vs control view), then the search times will differ, no question about that. You could try to limit Ranorex to "control" elements as well by adding a check for iscontrolelement='true' to your RanoreXPath.
atom wrote:We also see a bug performance different on TABLE elements, WHITE and UI Spy alot quicker than Ranorex
Do you experience this speed problem when working with Ranorex Spy or at runtime, when searching using RanoreXPath?
Do you use RanoreXPaths with "//" in them?
Is this a WPF or Silverlight application?

Do you have a sample application that we can reproduce the problem with?

Regards,
Alex
Ranorex Team
.
Image