Ranorex Forum

Hi,

The biggest problem I'm facing right now is a slow down in the recording mode as our repository grows. Our repository cs file has 40,500 lines of code in it. It currently takes about 10 seconds to record one button click in our software using this repository. This delay makes it impossible to make any new recordings with our software as it connects to other systems and the connection drops if the program doesn't respond every ~10 seconds ( with this recording delay the connection drops quite frequently ).

I have also been noticing my searches are getting really slow as the code grows larger. Our project is going to be getting much bigger as the current code base probably only covers about 3-5% of our software. I was wondering if this was already under investigation or if there was some sort of patch/fix for the issues I am seeing. It would be nice if you could do a search that didn't go through the recordings, as this would probably cut down on the search time some. Some sort of indexing search may help as well, I'm not sure what is currently being done.

There are probably some duplicate and/or unused items in our repository, but I have not seen of any way of dealing with these through the tool besides doing a search through the code for the item. A feature in the tool that did this would be extremely helpful.

Thank you for your help in diagnosing this issue.

Hi,

Would it be possible to send us the repository (rxrep and cs file) to [email protected] ?
We also have such big repositories and we didn't notice such problems.

Regards,
Peter
Ranorex Team

Peter,

Thanks for the reply. I've gone through the channels here and we cannot safely send out our repository as it contains some proprietary data. Is there any help you can give us through the forums or can we schedule to have someone come out and look at our issues we are experiencing?
I upgraded our solution to Ranorex 3.0 yesterday and the slowness is now even more apparent. There is a 15 second delay on startup and shutdown of Ranorex 3.0 when our solution is loaded. I've used the cleanup tool and our repository is not even that large anymore. In addition we have another project here that uses Ranorex and they are not experiencing any of these issues and their repository and recording count are much larger than ours.

Thank you for your quick reply

Hi,

so does the delay only occur on opening Ranorex Studio?
This happens, because the code of your whole project will be generated by opening the Studio to ensure everything works as expected.
Next question is what is the size of the Repository (the .rxrep file) compared to the Repository (the .rxrep file) of the other project.
Additionally, I would suggest to read the user guide, especially the chapter about Repository Seperation to get more information about how to manage your repository on a smart and well thought out way. Maybe the approach of meeting your requierements is to split up your repository, which might make evreything much more maintenance-friendly.

Regards,
Tobias
Support Team

No the delay occurs on startup, shutdown, and there is about a 10 second delay when hitting the play button (or doing a rebuild). I'm not sure how to tell you the size of the repository as I do not see a count of repo items anywhere, but the code size is 15,500 lines. I do not want to separate the repository into multiple repositories as that would make for a lot of duplicate items and would be very confusing.
The problem is that the delay makes Ranorex look like its going to crash. The title bar says "(Not Responding)" and the hourglass wheel appears on the screen for about 10 seconds. If there was a loading bar or some sort of progress bar then at least I'd know Ranorex was doing something and not about to crash.

Hi,

this is a performance limitation we are taking care of. So in future there will be no delay in shutting down Ranorex and the delay will drastically go down on pressing the play button.
But, as mentioned before, it is not recommended to implement a huge repository for all recordings, but to split it up for each recordings (see the documentation). This will, of course, improve the performance, thus in case of having one huge repo on every code change in one recording the code of the whole repository will be update. By splitting up the repository, only the code of the affected repository will be updated.

Regards,
Tobias
Support Team

Is a 15,000 code line repository too large? Previously my repository was 45,000 lines before the cleanup command was added in 3.0. The slowdown in recordings was also fixed in 3.0, I don't notice any slowdown when doing a recording. The problem is that with 3.0 I now notice the slowdown during startup, building, and playing back the recordings. This was not a problem in 2.3 with a repository almost 3x as big, but it seems to be a problem in 3.0.
If this is being resolved then we won't have any issues having 1 main repository. The problem with having multiple repositories is the amount of time it takes for someone to go through and cleanup all the Rx Paths every time new repo items are added. I've cleaned all the RxPaths in our 1 repository now and it contains a good portion of the items we'll need for our testing.

Hi,

as mentioned before the behaviour with the delays will be resolved in our next release.

Regards,
Tobias
Support Team

That would be really helpful! Other than that complaint Ranorex 3.0 is much easier to use, and easier to create and manage tests with.