Is there anything that can be done about the slow reloads when we apply settings on servers running in remote datacenters? It seems to keep getting worse with each new version of Freepbx. I think it is partly because of all the css and js that is loaded. It was never a problem with Freepbx v12. Seems to have started with v13 and I think it’s even worse on v15.
Disabling signature checking seems to help a little. We have never had that feature protect us from hackers anyways and they seem to have found ways around it now so we just disable it by default.
It’s just a standard install. From scratch on D9 or CE7 or distro. Doesn’t matter. This is remotely. Not local. And remotely up to 2000km away. Not local datacenters. The back and forth latency has a lot to do with it. It’s all kinds of datacenters and all kinds of installs. Not some isolated issue.
There is no such thing as a standard install. From the config side, reload times are greatly affected by extension count, user count, number of conferences/queues/etc. On the hardware side it will be affected by the host and vm resources. My colleague @slobera just did some testing on this, and found sub 60 second reloads for a 1000 user system with both conferences and queues.
Assume fresh install with all defaults and no entensions or trunks or anything else configured. Empty DB etc.
It’s usually just the first apply. After that the browser caches the css and js so subsequent apply is usually (but not always) faster. To continuously see it open the browser in incognito mode and do and F5 reload before each APPLY.
In a datacenter a few hundred miles away it’s fine. In a datacenter on the other side of North America it is really slow.
I am remote also, but our experiences seem to differ. If you don’t think it has anything to do with the size of the config, you can get more specific by opening the developer console and seeing which resources are taking longer to load.
There is something that is causing AJAX to wait but I am not quite sure what. Since it was only from browser, not command line, and usually just happening on the first apply I assumed it was waiting for uncached css/js to load. I’m not sure about that though.
The dashboard seems to load fine. That was a problem before yes. Where it sat saying “Loading” at 75% for awhile. I think that was related to signature checking where there was some change with the signature system and it wasn’t working or something. I haven’t seen that in awhile so I think that is fixed now.
I have read about that problem with DNS but I don’t have that problem because I already have that setting in my /etc/hosts.
How long should reloads normally be? I seem to be getting about 5 to 6 seconds on average with a nearby server with signature checking disabled but it still sometimes waits for up to around 15 seconds.
time fwconsole r
It really depends on how much data has to be pulled from the database and written to /etc/asterisk and what hardware is available to do it. It has NOTHING to do with your bandwidth to the server when done over SSH. Maybe FreePBX XX will use all realtime and there won’t be reload times.