That’s interesting, can you share what other features enabled other than Speedify, and an estimate of connected Wi-Fi clients?
I think you can mount /var to a pre-formatted ext4 SD-card in LuCI mountpoints menu for logs.
of course now that I’m watching it constantly there’s not been any problems.
Added vnStat2
Also added the bandwidth sharing under SQM as described on the wiki
I did have a low memory banner pop up in the speedify UI about an hour ago right around Uptime: 2 days. When I checked, speedify was top of memory use. And one CPU was showing pegged with speedify -d logs as the top process both CPU and Memory. I did /etc/init.d/speedifyconf restart and the memory use went down and the speedify -d logs is now in check
Enabling zram next release, upon further tests, Flint & Slate AX 5Ghz Wi-Fi driver use too much memory that is not freed when 10+ clients are connected.
Flint/Slate AX patch for testing, in terminal, type the following to enable zram:
Slate:
With zram enabled and swap on, used RAM seems to be holding steady now at the ~71% mark and free does show some swap in use. Before zram, all swap numbers were zeros.
root@SmoothWAN:/usr/share/speedify# free
total used free shared buff/cache available
Mem: 402612 278336 33768 448 90508 76044
Swap: 195312 5636 189676
root@SmoothWAN:/usr/share/speedify#
In terms of zram, it looks like there are luci settings instead of forcing something in rc.local wouldn’t it make more sense to use uci to keep it more obvious?
Good to hear, not sure if that option works on the unofficial OpenWrt build by GL.iNet, let me know if it does. Only one of the compression algorithms is available.
Will push a hotfix soon with zram enabled.
I wonder if the previous smoothwan versions are different, since I noticed that the official firmware 4.2.0 is using a bit more memory than 4.1 , and HF5 use the 4.2 base.
Don’t remember what Speedify usually used in terms of RAM unfortunately.
I do remember that it never reached hundreds though.