We are seeing extremely high IOPS and CPU usage when doing basic operations from Test Studio; such as deleting results.
If anyone can help me understand why this might be I would be for ever grateful! :)
We are running version 2015.1.528.0 on Server 2012 R2
The load seams to be coming from SQL Server that is running on the machine (part of the Storage Server?)
I can't imagine the software is so inefficient as to be making all these database requests unnecessarily so hopefully its a configuration issue? everything should be configured as it is out of the box.
2 Answers, 1 is accepted
0
Ben
Top achievements
Rank 1
Rank 1
answered on 24 Jul 2015, 02:47 PM
Bump
0
Hello Ben,
I apologize for the delay getting back to you. We are temporarily overloaded in support this week.
I'm not sure I understand what I'm looking at in your screen shot. Sure I realize it's a graph showing disk activity over a 55 minute period. However I don't know what to correlate it too... what action was happening at what point in time.
As for seeing high IOPS and CPU usage, unfortunately that is believable. The current DB schema is poorly designed and does cause excessive SQL resource use.
The good news is that this part of the product is actively in the process of being redesigned by our development team. We expect to have a new release with optimized DB storage sometime this year.
In the meantime have you already read and tried the suggestions from this KB article?
Regards,
Cody
Telerik
I apologize for the delay getting back to you. We are temporarily overloaded in support this week.
I'm not sure I understand what I'm looking at in your screen shot. Sure I realize it's a graph showing disk activity over a 55 minute period. However I don't know what to correlate it too... what action was happening at what point in time.
As for seeing high IOPS and CPU usage, unfortunately that is believable. The current DB schema is poorly designed and does cause excessive SQL resource use.
The good news is that this part of the product is actively in the process of being redesigned by our development team. We expect to have a new release with optimized DB storage sometime this year.
In the meantime have you already read and tried the suggestions from this KB article?
Regards,
Cody
Telerik