Progress® Telerik® Test Studio® Feedback Portal
Back to Feed
Request a Feature Report a Bug
Completed
Last Updated: 23 Apr 2015 07:33 by ADMIN
Ewin
Created on: 01 Apr 2015 16:58
Type: Feature Request
1
results view trying to loading old results
I have been using Test Studio for over three years now.  

I am consistently harping on the concept of memory management.  

In this feedback item, http://feedback.telerik.com/Project/161/Feedback/Details/125693-persistent-results-tab-view, I specifically asked on October 2nd 2014 about the results and what comes up.

Attached to this feedback item are two screenshots.  The first screenshot identifies that test studio is attempt to load a aiiresult file that is older than 1 month.  The second screenshot is showing test studio attempting to load a aiiresult file ran yesterday.  

I have 10 test studio automation projects that I manage.  In each project, I choose not to check the results into to TFS because it eats up space and is annoying to manage if I Get Latest.

I took some time to move the results files to a different folder so that the results will load faster. 

I feel that this is something that this activity is not necessary if the result view only loaded what is applicable to the largest searchable timeframe, which is a one month timespan.

http://feedback.telerik.com/Project/161/Feedback/Details/135352-test-studio-performance-and-memory-usage
Attached Files:
5 comments
ADMIN
Daniel Djambov
Posted on: 23 Apr 2015 07:33 
Telerik: we have implemented new results loading optimizations, which will load the results on demand for the time period selected only and navigating through timeline will load the new results. This will improve the performance and get rid of all such errors you are seing right now. The new implementation will be available in our next product release planned to be out early May 2015.
Ewin
Posted on: 07 Apr 2015 16:07 
In a previous feedback item I recall that the OOM exception described in the KB actually made the situation worse because now it just allow test studio to consume more memory than 2 gb.  

http://feedback.telerik.com/Project/161/Feedback/Details/125693-persistent-results-tab-view

Additionally, I am apparently not the only one that has this concern based on a different feedback item shown here: 

http://feedback.telerik.com/Project/161/Feedback/Details/114402-out-of-memory-opening-many-and-bigger-test-list-results
ADMIN
Daniel Djambov
Posted on: 07 Apr 2015 15:09 
Telerik: thank you for the additional details. I ckecked the log and it is indeed an OutOfMemory exception that occurs when loading the results. As I said before, even that we are not loading all the results completely, we load partially all the results to get their basic information from their header, which leads to OOM exception when the ammount of the results is huge. I will log an internal request to optimize loading of results further in cases like this. In the mean time, here is a workaround which can help you increase the Test Studio memory usage and bypass this issue (http://docs.telerik.com/teststudio/knowledge-base/getting-out-of-memory-exception-errors). Basically even if you are with 8GB or 16GB of physical memory, Test Studio is a 32 bit process that only uses 2 GB of memory by default, so any additional physical memory is not actually used. If you apply the above steps as a workaround you will start using 4 GB of memory for Test Studio, which will handle larger memory demands. Appreciate your feedback and will keep you updated on our performance improvements in future releases. Best Regards, your Test Studio team
Ewin
Posted on: 07 Apr 2015 13:28 
This error only occurs during the initial load of the results tab.  I have not had an error occur when viewing the results of a test list.  

When test studio loads, there is no problems with memory.  

But as soon as the test list results get loaded, there is definitely an issue. 

I initially thought that my computer just did not have the memory to support it with 8 gb.  But I had an upgrade to my work computer with 16 gb.  

This issue continues to occur regardless of the memory.  

Previously I reported a similar issue with the help of Cody Gibson about Visual Studio plugin continues to consume memory. 

http://feedback.telerik.com/Project/161/Feedback/Details/40448-appears-to-be-a-memory-leak-in-vs-plug-in-opening-and-closing-tests

I feel this issue is basically the same thing where the test results are being committed to memory.  But never released.  

http://screencast.com/t/xiS99sJNVlEk
Attached Files:
ADMIN
Daniel Djambov
Posted on: 07 Apr 2015 12:42 
Telerik: thank you for your feedback - we appreciate it. Here is a little more info on our current implementation for loading Test Results - you are correct that we are reading older results than the current time span, but we do not load them into memory - we only open and read their headers to be able to visualize basic information about them.We load more information only for the results of the current  selected timespan. When opening a result in Detailed Results View, we load the full result into memory, so we can get information from the tests associated with it. That is why when you open a result that is somehow corrupted (its json format is broken somehow, which is the actual problem here), we show an error that result cannot be loaded, even though we don't actually load the result, only read its header. Having a result that is broken will lead to this error until the result is removed from the project. With our latest release we also remember the Results View opened state, so when switching between tabs and going back to Results view, not to reload all the result headers again and persist the state where you left in Results view. Having said the above about result handling, do you have any more specific request for us to consider for improvement here?
Create an account Log In
View
Type
Status