nw.js preview and export build performance difference

Discussion and feedback on Construct 2

Post » Wed Aug 31, 2016 2:56 pm

Arima wrote:Does C2 use code protection when exporting to nw.js? If so, that means there's an extra ~30% performance hit as mentioned on this page: https://github.com/nwjs/nw.js/wiki/prot ... 8-snapshot

The compiled code runs slower than normal JS: ~30% performance according to v8bench. Normal JS source code will not be affected. Again, if you have a real need against this limit, please file an issue and we'll find time to fix it.


~30% is quite a lot... if C2 does use it, maybe we should have an option to turn it off.

@Ashley , what's you opinion about this?
B
128
S
33
G
17
Posts: 1,551
Reputation: 20,488

Post » Wed Aug 31, 2016 3:55 pm

No, we don't use NWjs code protection and so there is no performance hit from that. If you enable minification on export, you get good code protection anyway from the obfuscation.

There really isn't any good reason the performance would be significantly different after export - in fact I'd expect it to be better, since it has the advantage of using spritesheets after export, and a lot of preview-only JS code is stripped out.
Scirra Founder
B
387
S
230
G
87
Posts: 24,249
Reputation: 192,240

Post » Fri Sep 02, 2016 4:59 am

Ashley wrote:No, we don't use NWjs code protection and so there is no performance hit from that. If you enable minification on export, you get good code protection anyway from the obfuscation.

There really isn't any good reason the performance would be significantly different after export - in fact I'd expect it to be better, since it has the advantage of using spritesheets after export, and a lot of preview-only JS code is stripped out.

Thank you for taking the time to answer.
B
128
S
33
G
17
Posts: 1,551
Reputation: 20,488

Previous

Return to Construct 2 General

Who is online

Users browsing this forum: No registered users and 6 guests