Forum Discussion
From version 10 onwards, I noticed some performance degradation.
For me, unchecking and un-used extensions (not script extentions, full extentions), which are all switched on by default, got most of my performance back.
TestComplete comes with a pretty sizeable number of extensions (60+?). Most of my tests only actually need 6 or 7 of them.
(This has been discussed on here before. A few of us - myself included - would prefer they were switched off by default and you only switch on what you need. But I appreciate this may make life more difficult for those new to it. Or storing extension settings at project level. Which is probably a more workable solution.)
(For ref - I run TestComplete on a VM. My host machine is a Win 7 Pro 64 bit, i7-2600 with 16gb of RAM. The VM is lower spec than this. It all runs on a Samsung EVO SSD, which helps. Speed using TC11.20 is OK.)
Thanks Colin_McCrae, that was the ticket.
I cleaned up extensions that I knew where absolutely not required (and left some that were questionable) and that has completely eliminated the "not responding" problem. It really is a little surprising that SmartBear would elect to turn on so many extensions by default; particularly several different bug resolution applications at the same time!
Thank you again for this indespensable advise, it has made a world of difference...I can script again!
William
- Colin_McCrae9 years agoCommunity Hero
Good to hear.
Can't remember if we raised a feature request to have these stored at project level? Will check and raise one if not.
And a note to be aware of in future - every time you install an updated version of TestComplete, it will revert every single one of them back to "ON". You need to switch them off again after every update. And between projects if different projects rely on different extensions (which they invariably do).
- m_essaid9 years agoValued Contributor
Hi,
Thank you Colin,I don't mark it as "solved" yet only because I don't have the time to check which extension I have and which I don't have.
... but I'm sure it's ok now.
... but, as I'm still learning plenty of stuff about TE/TC I'm afraid to take off by this way functionnalities that could be helpful in the future. Functions that I still don't know yet.
- Colin_McCrae9 years agoCommunity Hero
You can just switch them all off. Switch on the obvious ones you know you'll need. Then run the test. If it's missing an extension it needs, you'll figure that out pretty quick when it fails, re-enable the needed one and try again.
You can't actually break the test by disabling extensions. Stop it working, yes, but it's not actually broken. If all else fails switch them all on again and you're no worse off than when you started.
Can make a world of difference performance wise. Some of my bigger suites run several hours so a 30% performance hit can make a BIG difference ...
Related Content
- 11 months ago
- 6 years ago