I notice that Wappler sometimes spins up the fan on my MacBook Pro.
I checked Activity Monitor and it seems that when Wappler is running it also launches multiple instances of something called “nwjs Helper” and all combined they take up over half my CPU. See screenshot below…
I’m working under the assumption that nwjs Helper is Wappler related because when I quite Wappler all the nwjs Helper instances disappear from Activity Monitor. A quick google search explained that nwjs Helper has to do with Node.js apps and my guess is that Wappler itself is written in JS/Node.
Is nwjs Helper required for Wappler to run properly and, if so, is it normal for Wappler to spin up multiple instances of it?
Wappler was loaded, but not actively being used. It was just sitting in the background not doing anything, but as you can see from my earlier Activity Monitor screenshot, the combined CPU usage of Wappler and nwjs Helper was high.
Wappler uses a lot less than Dreamweaver, which hogs about 60% CPU, however if I load Wappler and let things settle, it uses really low resources.
Below is a screenshot of my usage and also my machine details. I use a MS Surface Laptop, which is really useful for my puposes and link that to a docking station, which then runs my 27" Dell 4K screen for office use.
A big update is coming up tomorrow, we are updating the core to the latest Chrome 85, which has huge performance improve ta and lot of less memory usage!
Page I have open is a regular PHP file created in Wappler. Nothing fancy.
If I switch to a completely different project it behaves the same.
When I close all windows (within Wappler) it remains at 130% CPU for NJW helper (renderer) and Wappler itself at 0.1%.
Not using a monitor, just working directly on my Macbook without external keyboards or mouse. No antivirus that interferes.
I was having a lot of performance problems due to docker desktop for mac(already mitigated in latest versions of Docker), using AV software and changing from hdmi to displayport.
try closing Wappler completely (right quit from the icon in the system menu above) and make sure no other nwjs Helper processes are running on the background. Then start Wappler again.
It might happen that you have a runaway background process called nwjs Helper - that is somehow remaining of previous instance - and that is sucking the cpu.
I am having issues as well. It takes me now 8 seconds (which was nearly instant prior to the release) to display the results of a simple search on table. In browser mode it renders the results instantly. (Using Docker locally). Using the View Toggler, in Wappler, it takes 8 seconds for something that was rendering instantly prior to the new release. I am on a Mac with the latest version of Catalina. Below are my screenshots of the CPU and Memory of nwjs. I took these screenshots after quiting Wappler and restarting. Note: All nwjs CPU and Memory processes ceased after I quit Wappler.
LOL. Docker, Wappler, Notes, security video, Dropbox Accounting, financial apps, a bunch of browsers, Windows 10 with some apps, and 3 monitors on my Mac. LOL
