Skip to content

Conversation

@volkjohn
Copy link
Contributor

The SCCP Phone Manager page was taking over 12 seconds (on very old hardware) to load for me (with ~15 phones configured). After some profiling, I saw sccp_manager was truncating the sccpsettings table on every pageload, then inserting the exact same settings back into the database. This was severely hurting my ability to configure phones in a timely manner.

It seems there are many ways to optimize sccp_manager to reduce page load time. I focused on only saving the difference of sccpvalues in order to achieve around 6x speedup. Now when loading SCCP Phone Manager page, sccpsettings will not be truncated. Instead settings will be updated by row as needed.

Please let me know if you would like me ot refactor, rename, comment, or test this some more. I was able to change phone and line settings, as well as server config settings with the new code.

On each page load the sccpsettings table would get truncated and repopulated with the same data causing a big bottleneck. Now we will only attempt to save settings to the DB that have changed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant