Forum Discussion
I am seeing the same issue as well. I am in the process of converting our codebase to JavaScript but our smoketest performance has increased by 20min! I have not been able to find a solution - have you?
Hey Blake,
I raised a support case with the the Customer Care Team for this issue. After looking at my project, they acknowledged/confirmed the speed degradation in the converted JavaScript project and advised that there is no solution for it, for now. They may look into it in future releases.
Some areas in JavaScript execute faster than JScript but overall, the JavaScript project works much slower for me. So my project remains in JScript!
- Blake_Bryce8 years agoOccasional Contributor
Good to know. We made the decision yesterday afternoon not to convert to JavaScript.
- tristaanogre8 years agoEsteemed Contributor
I have a question:
Are you actually doing the "conversion" of the project (right click on project, select Convert to JavaScript, make code modifications) or are you doing all this conversion manually?The reason I ask is, if you are doing the conversion using the built in convert function, what does performance look like if you simply port the code over to a new project configured to use JavaScript with non of that conversion? I don't know if it really makes a difference but more of a curiousity thing.
- AshMan8 years agoNew Contributor
Hi Robert,
I did the conversion of the project using right click project and convert to JavaScript method. However, I think the performance issue is with JavaScript engine in TC.
In my project, I did investigate the performance issue (before contacting support) and narrowed it down to data comparisons, actual vs expected. I was using aqObject.CompareProperty(pStrExpectedVal, cmpEqual, pStrActualVal, false, lmNone) for the data comparisons and then changed it to equal(pStrExpectedVal, pStrActualVal) and it made no difference.
To do some base-line comparisons between the JScript and JavaScript engines, I created a for loop with 100 iterations to do:
1) a simple calculation,
2) compare the calculated value with a fixed value
3) output a line with Log.Message() if the comparison failed
It took about twice the time to run in JavaScript than in JScript. Increasing the number of iterations made it worse in JavaScript!
Related Content
Recent Discussions
- 3 days agovladd1