There is a new method for loading pages using AJAX user interface (UI) following the introduction of SugarCRM version 6.3. It loads html contents instead of making a full page refresh. Below are some major advantages that this method has to offer on SugarCRM performance.
Server load is reduced
There is no need for the server to deliver the footer, header, or examine style files, and standard javascript for each request.
Full rebuilding of the Dom tree is not necessarily required
The center area of the content is set to be modified instead of destroying or rebuilding the whole Dom.
Script files are not longer required to be parsed
Generally, the loading of pages requires the browser to parse all of the scrip files and reload into the memory even though there is a caching of javascript files. Performance is boosted when the javascript to the current page is parsed. This is evident in machines having slow CPU speeds but showing fast internet connection.
The number of request per page is minimized
There are no more problems encountered during the configuration of a web server to set cache timeouts that are very large. The image, javascript and style files for request are only loaded by the client once. A request is never made again unless there are new updates in SugarCRM. Unfortunately, a request to the server is still needed by the client because of several non-configured web servers. But with the new Ajax UI, these script files can stay in the memory until the browser is closed by the user even if configuration of the cache expire is not made. This can make the load time of a web page to a single request that takes under a second.
Note:
The addition of AjaxUI also brought some adverse impacts in terms of customizations.
• The custom javascript that uses document.write can replace the current web content due to the fully loaded Dome tree when the web page is rendered.
• Because of the loaded web page before the insertion of the main web content, onLoad can no longer be trusted.
• The order of scrip block execution is a major javascript issue.
