I have what I think will be a controversial opinion. I think Luci should be scrapped and that something more like Luci2 should replace it.
It would be nice too, if the instructions for installing Luci2 were updated on the wiki. So that people could test it.
I will mention too that OpenWrt snapshots do not ship with Luci installed, so you likely won't experience the issue if you use one. You will however, need to configure your OpenWrt instance via ssh instead of over http in the absence of Luci.
I'm in the process of writing my own http configuration tool and it's in the early planning stages because of the very issue mentioned in this thread.
@jow I noticed that the proposed fix was reverted. From the commit message, it wasn't entirely clear in which situations we do need concurrent HTTP requests. Could you perhaps elaborate? Would it be safe to keep concurrency disabled if I don't run into any issues with it disabled? Thanks!
this is true, while lowering script requests to 1 does help a bit it is not complete solution and slows down additional radios processing. there is another bug, as even with this change just by overviewing wireless page load on my litebeam 5ac reached 1.60
I was able to improve performance noticeably on my box (less latency and no freezing on LuCI page loads) by switching the SSL library to mbed TLS. Maybe it's just me but mbed TLS seems to perform better on devices with less processing power.
Yeah, it's kind of in the name "embedded TLS library"
I guess I should have clarified, mbed TLS seems to work better on my ar71xx devices than my mt7621 devices, and the OpenSSL seems to work better on my mt7621 devices than mbed TLS.