nw.js preview and export build performance difference

Okay, just made a couple of short clips showing just how much difference I get between preview and export. The export running in the clip is win32 but win64 is no better, in fact it might be worse even. Hard to say.

Running on intel iris 6100, same as in the original post. This nwjs version is 16 and the C2 version is r232.

Preview - very smooth:

https://dl.dropboxusercontent.com/u/705 ... 165437.mp4

Export win32 - not so much:

https://dl.dropboxusercontent.com/u/705 ... 165349.mp4

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

[quote:1i3vnw8n]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.

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

[quote:34rhtxj8]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.

Would be nice to know this. +1

Ooh that's Interesting. If that's what's going on then +1 for a toggle if possible.

If that's the case then I also add my +1 to this.

Would be nice if this could be implemented on the go, together with my recent NWjs suggestion.

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

[quote:36cfmh4p]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?

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.

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.

ErekTHey man, have you solved your problem?

I have the same issue. My game runs smooth on preview, but when I export it starts smooth and gets slower in function of time. It gets so slow that it becomes unplayable.

I'm kind of desperate. Why does this happen and how to fix it?

Ashley said that .nw should be faster, but I think he doesnt imagine all the nuances involving the application.