Forum Discussion
- culisseContributorI'd just like to update that my decreased performance issues that started with Release 9.0 seem to be totally fixed with Release 9.3 which was released yesterday June 10th. In fact, it seems to be even faster now and I've finally upgraded my last machine from 8.7 to 9.3. Thanks guys!
- agabrielContributorThis may help some others out ...
I went from using a old machine (Dual Core - 4Gb RAM) to a newer one (Core i7 - 16Gb RAM), both on Win7, and saw a dramatic DECREASE in performance (ie. a test that took a few seconds now took 4 mins).
In my case, the problem was corrected by changing 2 things:
1. I was using Performance Indicators that named the old machine. Changing them to the current system made the difference.
2. I changed the CLR Briding to 'same as OS' and enabled Multi-Threading.
My tests started to run at optimal speeds for the machine that I am now using. My tests now run exactly twice as fast!
I hope that helps at least one person! - Hello everyone,
I was also facing serious performance problems when creating operations like On-Screen Actions (I am working on keyword-tests with activated NameMapping) within my test suites. It took about 2-3 minutes to select an object! This problem unfortunatellly was not fixed with the upgrade from 9.2 to 9.3.
But after some research I discovered that the activated Windows 7 Aero-Design seemed to be the cause of the performance problem. I am using my testmachine via Windows RDP which might be relevant for this issue as I can not remember similar problems when working on my native computer.
Be sure to have not selected an Aero-Design even though Windows might tell you that "Due to remote control at least one design was deactivated" which might let you think that therefor aero-designs are not working anyway. In addition be sure to restart the machine after changing to a non-Aero-design (in my case only than the problem was fixed).
Maybe this description is of any help for someone else.
Kind regards - irina_lukinaSuper Contributor
Hi Egor,
Have you tried using tips from the following web page?
http://support.smartbear.com/articles/testcomplete/test-playback-performance-tips/I hope this information helps :)
- EgorKaOccasional ContributorHello Irina,
I've already tried this tips,but nothing happened.
I rolled back to previous version, now it works without problems.
Thanks any way for your help
Best regards,
Egor. - irina_lukinaSuper Contributor
Hi Egor,
I rolled back to previous version, now it works without problems.
TestComplete 9 includes a number of helpful features, and I'll try to help you so that you could use this version for your tests. For this purpose, please follow the instructions below:
* Reproduce the problem in TestComplete (that is, run your test two times) so that it generates test results for each test run.
* Add the entire project (along with all of the test results) to an archive.
* Post this archive here or send it directly to our Support Team via the SmartBear Software Support web form.Thanks :)
- teddy77777ContributorWe also just upgraded from v8 to v9 and are also seeing slow performance using v9. We are seeing TC9 as about 30% slower during playback.
This happens on the same machine and the same project without any changes to either other than TC8 vs TC9. - sastoweSuper ContributorPlayback over here is super slow as well. I am working a number of other tickets, so cannot work another at this time. But I wanted to add my support for this being looked into.
- gnivlagOccasional ContributorBump. Test execution using TestExecute went from around 50 minutes to 2-2.5 hours when upgrading from 8.60 to 9.0. I already upgraded my project already to 9.0 and have made other changes already, so it looks like I can't even go back to 8.x without significant efforts. Since I see so many people experiencing similar behavior, is SmartBear aware of an issue regarding test execution slowness?
- AnonymousAll:
the issue is on top of the priority stack of the team. We understand that it may not always be possible to share with us the test projects and examples, but we would appreciate all assistance in identifying the crucial details (as they always are with performance problems) with respect to this reported performance degradation.
While this very unfortunately did not help in the situations described above, we do have performance regression tests that we track release to release.
We very much regret the resulting challenges in your testing, and intend to fix the issue in the shortest possible order.
Related Content
- 3 years ago
Recent Discussions
- 2 days ago