Wappler 7 performance issues - MacOS

[daves88]

Hi Wappler Team,

I am currently on the latest version of Wappler 7 on a Macbook pro (2.3GHz i9 and 32GB of RAM). It's a decent machine with plenty of grunt.

When I open Wappler for the first time upon booting up it works great. Then it gradually slows down and performance becomes very poor. After a few hours of use eventually it just freezes and I need to exit Wappler and restart it.

I never had this issue with Wappler 6.8.0.

Anyone else having this issue?

Thanks

[guptast]

Hi David,

Yes, I have the same issue on MacOS and I'm noticing performance issue more with the latest version 7. I have MacBook M2 Pro with 16GB RAM. After using Wappler for about an hour or so, the memory usage gets up to ~2GB from the starting memory of ~500MB, and the app becomes slow to respond. I have to restart Wappler to free up the memory and get the performance back to normal levels.

[sitestreet]

I'm on a Mac Studio M1 and a MacBook Pro M2 Max and both are left running for weeks on end without any issues. I've kept up with the latest version throughout.

[mebeingken]

Yes, issues every day. I’ve been trying to make a proper bug report but haven’t had time or anything particularly useful.

One suspect for me is the dynamic bindings selector panel. I feel like the search for elements in that is overloaded. Or maybe that is just where I see it the most.

[bpj]

I see regular problems too. I've reported it before and find it is most obviously problematic when there are modals/conditional regions/ collapses on pages - my theory is that they aren't being destroyed each time the design window is refreshed (especially as it refreshes with pretty much every keystroke in code view)

Increased memory usage when working in Code View

Not sure if it’s related but I get a LOT of memory usage and system slowdown on pages with modals (tends to be where there’s a few modals) - just wondering if they’re not being properly destroyed when redrawn in the design preview. As you edit, particularly in code view, frequent refreshes make it slow down. The main project I see this on is an older BS4 PHP one - just in case that makes a difference (that is also the only one I have with such heavy modal usage)

[George]

in Wappler 7.1 we have greatly improved memory usage. So you shouldn't see big increase on longer usage. Even more memory optimizations are coming up in the next update

[bpj]

Hi @george,
glad to see more improvements are coming - sadly, I'm not sure that the last release made too much difference (but I really do appreciate that you're giving it some attention)

[George]

How many open html editor tabs do you have?

[bpj]

At the time of that I think it was only 3

[bpj]

I only have 3 open now and I'm up to 3.8GB

[patrick]

Were you working in the same editors the whole time or did you close editors and open new ones?

[bpj]

I think I might have closed one tab and opened another but in the last hour I've had the same tabs open and Memory has continued to rise:

[George]

Could you try again with clean Wappler start for an hour and describe your actions, tab editors open, close, pickers, and what was the memory before and after.

[bpj]

1. Open (after full Docker close & Wappler close from system tray)
2. Initial Memory after open (3 eps pages on start & Wappler Dev server running)

3. A few mins in - just adding an SC to a content page

4. A few mins later - creating button group and linking buttons to SC component

5. A couple of mins later (copy and pasting an entire div in code - complete tags with no errors)

6. Often (but not always) accompanied by a 'freeze' that indicates a CPU spike (lasts a few seconds and UI totally unresponsive):

[bpj]

It is worth noting that this page has a few conditional sections, a couple of modals and off canvases. I mainly work in split view and find it much quicker to use code view for most of my edits. When working I have App Connect disabled from the lightning bolt in the toolbar (it is my chosen system default)

If you need to know anything else, let me know

edit:
As an example, I simply added the disabled class to a button (typing in code view) and the CPU spiked and UI became unresponsive for about 5 or 6 seconds. I'm sure there's something going on when the design view refreshes - it is most evident, like I have said several times before, on pages that have a combination of multiple conditions/modals/off canvas/repeats etc.

edit2:
Ruling out spec, I am working on Mac Mini with M4 Pro and 24GB RAM

[Cheese]

@bpj

I'm sure there's something going on when the design view refreshes

Has been doing this for a while. I've upgraded my laptop recently to an i9 with 32gb of memory so not noticing it as much as I used to. Definitely the constant refreshing I'm sure of it but then I'm no expert so am just agreeing with @bpj as in this seems the most likely culprit for the issue.

[bpj]

It's such a time-consumer that I'm now doing most of my coding in Visual Studio where I can work as fast as I want. It's a shame because I really want to be in Wappler doing everything

[George]

Thanks for the details. Do you have some heavy pages that we can test with? Send as PM