Finding that opening several pages one after the other is causing some crazy memory usage in 7B/12. The pages are efficient and contain no errors, they don't even have dynamic data in them yet (have also tried more than one Project and the same result). Have restarted (laptop and Wappler) and did the same again and memory continues to spiral towards the stars.
I'll update to 7B/14 now and check again and see if there is an improvement.
Not much better at all. Something to try...
- Start Wappler and look at the initial memory usage, not too bad.
- Open a few pages, pages with something in them not just blank.
- Memory goes up, obviously now there are a few pages being rendered.
- Now close the pages and leave one open.
- Check your memory again, not so good.
Memory usage should decrease as now only a single page open and being rendered but this is not the case. The memory usage still remains high.
On my MacBook with about 10 pages open it barely goes over 400MB. What operating system are you using?
Ubuntu 24.04.1 LTS
In the eyes of Teodor this is a real mans OS...
Outside of Wappler it is incredibly efficient and barely scrapes the surface of my resources. This has only been occurring for a short while though, maybe over the last couple of Beta versions. I only have 12gb of memory so can't afford to waste any. Although a new laptop is on the cards in the new year at some point (hopefully in the first quarter) I'm stuck with this one for now (which has always been very dependable). This could very well be an Electron issue and not a Wappler issue though! Chrome is an utter stinking pig of a thing...
I posted about the significant increase in memory usage some time ago (v6.8). This is still happening in v7b14. (MacBook Pro, M2).
The main reason seems to be an instant refreshing of the design view when making any modifications in the code view. Over a short period of time, the constant refresh process begins to consume more and more memory, and the code view starts lagging and becomes slow to respond. The memory usage stays fairly stable while working with the APIs.
1 Like
Well we do use chrome internally and each page is isolated so opens a new process with its memory usage and chrome is known to be not the most memory efficient browser.
What you can check is, if the memory is well released after the pages are closed.
And also on what type of pages it occurs - just web pages with design view or also on server connect editors?
Interesting post…
I’ve worked almost totally with server connects in the last few weeks, but needed to work on the front end yesterday and found Wappler became quite sluggish…
This seems to be the issue for us @George
In our case the pages are very simple in relative terms. Currently they have no Server Connect Actions within them. JS and CSS only, with Bootstrap and Moment from CDN sources. Really spikes when App Connect Mode is active. Still memory is not fully released when the pages are closed (just a little drop in memory is noticeable, a hundred or so MB).
We updated to the latest Beta last-night and are still experiencing pretty much the same although not quite up to the 1.6gb shown above it is still around the 900mb - 1.4gb (fluctuating) level with just a few pages open.
My laptop is not the greatest but it is reliable.
- Ubuntu 24.04.1 LTS.
- Intel® Core™ i7-4710HQ × 8.
- 12,0 GiB Memory.
- 960,2 GB SSD.
Still have to say the new Beta is the absolute dogs bollox! A Brits way of saying its really really nice, and loving what you guys have done. Amazing work gentleman!
Hmm could you trace it back to previous betas or Wappler 6.8 when it was ok?
Strange, here is my set up and I have no noticeable memory/performance problems at all on my 5 year old MacBook?
And on a typical session I am running:
- Wappler 7.b14
- Chrome
- Navicat
- MAMP PRO
- Outlook
- Microsoft Teams
Here is my usage:
Think I've pinned it down @George
I noticed it when commenting some lines and every few characters the page refreshes, so if that comment was a sentence 'This is a comment so you remember what you did last weekend' the page refreshed half a dozen times during writing it. And on top every action within the page en tales a refresh. Thus if you work quite fast there are an awful amount of refreshes occurring. This seems to be the issue and this is when my fans ramp up considerably.
2 Likes
I have also noticed the same issue; the instant refreshing of the design view when working in the code editor significantly increases memory usage.
1 Like