nw.js preview and export build performance difference

Discussion and feedback on Construct 2

Post » Thu Mar 24, 2016 8:12 am

I don't understand either why the 64bit version uses more CPU. But as far as I know, the 32bit version will not be able to use more than 4GB of memory.
B
135
S
33
G
17
Posts: 1,559
Reputation: 20,732

Post » Thu Mar 24, 2016 8:13 am

LaDestitute wrote:It seems pretty obvious, but 64-bit NW is intended for developing on a 64-bit system, while 32-bit NW is intended for developing on a 32-bit system.


My system is 64 bit, OS and CPU.

64 bit NW always runs worse. By a lot.

It's not like this in other games.
B
70
S
24
G
19
Posts: 1,757
Reputation: 17,616

Post » Thu Mar 24, 2016 8:34 am

The way I see it all you really get out of 64-bit is lower compatibility. And no 4 GB memory limit. But I don't think any of us will make an asset behemoth so big it blows that budget anyway :P

In any case, I think I should make a bug report out of this. @Ashley: Is it okay to PM you a .capx soon-ish?
B
39
S
16
G
6
Posts: 543
Reputation: 7,619

Post » Thu Mar 24, 2016 12:43 pm

Cpu isn't the thing to worry about.
Fps is.
Image ImageImage
B
171
S
50
G
179
Posts: 8,382
Reputation: 113,458

Post » Thu Mar 24, 2016 1:17 pm

But a high cpu use tends to correlate with frame drops. Just to be sure, I repeated my tests and added a dropped frame counter (running test for one minute, the counter ignores the first 10 secs because they are usually terrible):

Preview win32: cpu 35%, dropped frames: 4
Export win32: cpu 33%, dropped frames: 5
Export win64: cpu 41%, dropped frames: 17

So, IMO, win64 wins the "not useful" export competition.
A big fan of JavaScript.
B
76
S
20
G
74
Posts: 2,249
Reputation: 46,472

Post » Sat Aug 20, 2016 6:10 pm

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
B
39
S
16
G
6
Posts: 543
Reputation: 7,619

Post » Sat Aug 20, 2016 7:40 pm

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.
Moderator
B
95
S
34
G
33
Posts: 3,007
Reputation: 27,876

Post » Sun Aug 21, 2016 10:42 am

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.

Would be nice to know this. +1
B
135
S
33
G
17
Posts: 1,559
Reputation: 20,732

Post » Sun Aug 21, 2016 10:52 pm

Ooh that's Interesting. If that's what's going on then +1 for a toggle if possible.
B
39
S
16
G
6
Posts: 543
Reputation: 7,619

Post » Mon Aug 22, 2016 5:28 am

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. :)
ImageImageImage
B
63
S
23
G
78
Posts: 664
Reputation: 44,941

PreviousNext

Return to Construct 2 General

Who is online

Users browsing this forum: Yahoo [Bot] and 10 guests