Completed
Last Updated: 23 Sep 2015 12:58 by Ewin
Ewin
Created on: 06 Aug 2014 21:34
Type: Bug Report
1
test studio performance and memory usage
I have previously reported this issue when back when: 
/Project/161/Feedback/Details/40448-appears-to-be-a-memory-leak-in-vs-plug-in-opening-and-closing-tests

It has been a year since I originally submitted that.  

From then and until now, I have not seen significant changes in test studio's memory management.  

Please perform a thorough review of test studio's performance on memory usage.  
10 comments
Ewin
Posted on: 23 Sep 2015 12:58
thanks
ADMIN
Konstantin Petkov
Posted on: 23 Sep 2015 07:21
Hi Ewin,

I assume you mean this feedback is obsolete now so thanks for the update!

Regards!
Ewin
Posted on: 31 Aug 2015 14:58
@Telerik, Please mark this feedback item as done. 
 
Ewin
Posted on: 02 Sep 2014 20:06
here is a dump process file from task manager. 

https://bamtechnologies-my.sharepoint.com/personal/ewin_hong_bamtech_net/_layouts/15/guestaccess.aspx?guestaccesstoken=E32tuwKL%2fiEB4X3AWYnXYg5%2b98kYG0RaetSZnxY24gI%3d&docid=0d8b263dbcc2d475683c8a0f44034d8e9
Ewin
Posted on: 19 Aug 2014 20:33
Related to this issue, after debugging a test, updating a element is extremely long time.  

You will notice in the first screencast, my ram gradually cycles from a 1.1 gb and then releases ram to show around 500mb.  

http://screencast.com/t/1WzdHdaFR65F

http://screencast.com/t/QONQesJeZDu

Ewin
Posted on: 15 Aug 2014 17:51
Demonstration of current areas noticing memory usage is probably used heavily. 

http://screencast.com/t/Am6u3gs9

I will probably do another screencast where it keeps going up.
Ewin
Posted on: 13 Aug 2014 13:49
I never get OOM exception like this KB describes. 

This probably does not occur for me because I have Windows 8.1 at 64bit.  

But from a user perspective, I should not have to be aware of the application's memory usage.  Since I even watch test studio's memory, this need to watch memory is a hindrance to my productivity and efficiency.  

All I ask is to have some performance testing and analyze how test studio manages its memory usage.

http://docs.telerik.com/teststudio/user-guide/knowledge-base/oom.aspx
Ewin
Posted on: 13 Aug 2014 13:17
Considering that Test Studio itself does not offer plugin to the standalone application, this idea of custom plugin is irrelevant.  Another thing, I have been a user for almost 3 straight years now and as such, I use test studio to close to its max capability from test creation to test list runs which goes back to test repair and the cycle repeats itself.  

With the initial launching of the test studio application, it takes about 400mb of ram.  Then over time going from test list results to test and back, the memory slowly creeps to unnecessarily large amount (1.1gb of ram usage alone).
Elo
Posted on: 13 Aug 2014 12:31
If you are running custom plugins you should acknowledge the fact that any of these could cause telerik teststudio process to leak memory.

You could try and disable any of these custom plugins if you have any.

regards
Ewin
Posted on: 08 Aug 2014 19:06
I expect there are times where test studio would take some memory, but it should not need to take up this much memory to do what it needs to do.
Attached Files: