NW.js Performance is worse than Chrome.

Post reply

❤Follow Topic(5)

0 favourites

4 posts

From the Asset Store

Firebase Utilities PRO- Analytics, Dynamic Links, Remote Config, Performance, Crashlytics

$12 USD

Firebase: Analytics, Dynamic Links, Remote Config, Performance, Crashlytics on Android, iOS & Web Browser

Sparsha

- VinniePin
- - Joined 28 Feb, 2018
  - 11 topics • 41 posts
- 2
- 4 May, 2023
- Quote
I created a simple project that has no events other than setting the text object's text to the current framerate. The project is configured to use full ticks with no vysnc to compare performance. When running the game in a web preview i get 106k frames per second, when running the exact same project as a nw.js export, i get 38k frames per second. Any thoughts? Perhaps we should use Electron instead?

Shoutout to LukeW on the discord for, more recently, discovering the descrepenacy.
Tagged:

nwjs
performance
- LukeW
- - Joined 26 Mar, 2017
  - 63 topics • 353 posts
- 1
- 4 May, 2023
- Quote
I ran this test today on two separate PCs. My scores were:

PC 1:

editor: 158,000

nwjs: 54,000

PC 2:

editor: 80,000

nwjs: 30,000
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- Ashley Construct Team Founder
- Moderator
- - Joined 21 May, 2007
  - 669 topics • 30,356 posts
- 3
- 4 May, 2023
- Quote
These results are pretty misleading. Think in terms of frame times, instead of frames per second: the first is doing a frame once every ~9 microseconds, and the second is doing a frame once every ~26 microseconds. So NW.js probably has a per-frame overhead of ~17 microseconds. A typical frame at 60 FPS takes 16.7 milliseconds. So NW.js is adding an overhead of about 0.1% per frame. In other words the difference is negligible and there is no point worrying about it.
- VinniePin
- - Joined 28 Feb, 2018
  - 11 topics • 41 posts
- 2
- 4 May, 2023
- Quote
I orchestrated a different way of testing it. Spawned a bunch of semi transparent circles with sine behaviors until fps was consistantly below 50 then stopped and displayed object count. Looks like nw.js has a 7% performance reduction over running the game directly in chrome preview.

Not nearly as bad!