Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-16562

Improve performance of loading the TinyMCE editor and macro browser

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Even with browser caching, IE seems to be taking 2-3x longer to render the addpage/editpage.action due to the added complexity of the js resources involved.

      This leads to full render times of 6-14 seconds in situations where the cache is purged/caching is disabled. (times taken from fiddler parses from localhost).

      This is in contrast to FF taking half the time on the same test system.

      Although consistent with the benchmark values taken from this source, 6 seconds to load a page without network latency is slow.

            [CONFSERVER-16562] Improve performance of loading the TinyMCE editor and macro browser

            Agnes Ro added a comment -

            Despite the fact that IE renders slower than other browsers, we have done our best to try and improve the performance in IE for Confluence 3.1. Browser load times is quite difficult to measure, but we have seen improvements in our internal systems with our current development release. If users find that the performance of the edit page is still an issue in 3.1, please raise another ticket and we may revisit it again in 3.2.

            Cheers,
            Agnes

            Agnes Ro added a comment - Despite the fact that IE renders slower than other browsers, we have done our best to try and improve the performance in IE for Confluence 3.1. Browser load times is quite difficult to measure, but we have seen improvements in our internal systems with our current development release. If users find that the performance of the edit page is still an issue in 3.1, please raise another ticket and we may revisit it again in 3.2. Cheers, Agnes

            IE has a very slow JS engine. Firefox 3.5, Safari and Chrome all have much faster JS engines. That simply is just the nature of IE to render JS-heavy pages slowly.

            T. J. Brumfield added a comment - IE has a very slow JS engine. Firefox 3.5, Safari and Chrome all have much faster JS engines. That simply is just the nature of IE to render JS-heavy pages slowly.

            Somayya,

            Our practice at Atlassian is to set the issue to resolved when we commit the change during our development process. We are indeed aware that this does not correlate to when the new version is released. In this case, we are still pending the release of Confluence 3.1, which will contain this improvement.

            Jeremy Largman added a comment - Somayya, Our practice at Atlassian is to set the issue to resolved when we commit the change during our development process. We are indeed aware that this does not correlate to when the new version is released. In this case, we are still pending the release of Confluence 3.1, which will contain this improvement.

            The status of this issue is RESOLVED when the comments from Atlassian is that it is open. I have issue CSP-39639 open for the same issue, and we need someone to escalate this issue not treat as resolved when in fact it isnt. don't you agree.

            somayya el gemei added a comment - The status of this issue is RESOLVED when the comments from Atlassian is that it is open. I have issue CSP-39639 open for the same issue, and we need someone to escalate this issue not treat as resolved when in fact it isnt. don't you agree.

            Agnes Ro added a comment - - edited

            We have decided to further address this by delaying the loading of the macro browser. The macro browser will only be loaded on the fist time it is opened.

            Agnes Ro added a comment - - edited We have decided to further address this by delaying the loading of the macro browser. The macro browser will only be loaded on the fist time it is opened.

            Agnes Ro added a comment -

            I'm not convinced we can close this yet, reopening for at least more testing.

            Agnes Ro added a comment - I'm not convinced we can close this yet, reopening for at least more testing.

            Agnes Ro added a comment -

            There is no simple workaround for this as it isn't a simple (or single) fix. Even worse, I may have to reopen this issue as the javascript tags will still be served in the header (due to plugin breakage) by default in 3.1. Instead there will be a configuration to turn on to serve the scripts at the bottom of the page. Eventually in a later release we will serve them at the bottom as the default.

            Agnes Ro added a comment - There is no simple workaround for this as it isn't a simple (or single) fix. Even worse, I may have to reopen this issue as the javascript tags will still be served in the header (due to plugin breakage) by default in 3.1. Instead there will be a configuration to turn on to serve the scripts at the bottom of the page. Eventually in a later release we will serve them at the bottom as the default.

            I've also reported the issue with long load times when editing and was referred to this issue. This is going to delay our roll-out as first impressions are vital to the success. If you know of a work around or have an early deployment fix that will resolve this please let me know. Changing browsers is not possible.

            Bill Campbell added a comment - I've also reported the issue with long load times when editing and was referred to this issue. This is going to delay our roll-out as first impressions are vital to the success. If you know of a work around or have an early deployment fix that will resolve this please let me know. Changing browsers is not possible.

            Agnes Ro added a comment -

            Updating title to be a bit more generic.

            Agnes Ro added a comment - Updating title to be a bit more generic.

            Agnes Ro added a comment - - edited

            Hi guys,

            I have been investigating into this issue and believe the IE edit page slowness is due to a number of things introduced in 3.0. There will be a number of tasks I will be looking at doing, so here is an update of what will be done for 3.1:

            Javascript tags will be moved to the bottom of the page

            See CONF-12329.
            CSS will continue to stay at the top, so pages will 'appear' to load faster. This should also help on the edit page.

            IE6 404s for some images

            We will be fixing the 404s returned by some images served in css files (due to usage of relative urls).

            Optimize the macro browser javascript

            I actually did find that rendering of the macro browser contributing to the edit page slowness in IE, so the script will be optimized.

            Sprite image for macro browser icons

            This should greatly reduce the number of requests made to the server.

            Cheers,
            Agnes

            Agnes Ro added a comment - - edited Hi guys, I have been investigating into this issue and believe the IE edit page slowness is due to a number of things introduced in 3.0. There will be a number of tasks I will be looking at doing, so here is an update of what will be done for 3.1: Javascript tags will be moved to the bottom of the page See CONF-12329 . CSS will continue to stay at the top, so pages will 'appear' to load faster. This should also help on the edit page. IE6 404s for some images We will be fixing the 404s returned by some images served in css files (due to usage of relative urls). Optimize the macro browser javascript I actually did find that rendering of the macro browser contributing to the edit page slowness in IE, so the script will be optimized. Sprite image for macro browser icons This should greatly reduce the number of requests made to the server. Cheers, Agnes

              agnes@atlassian.com Agnes Ro
              twong Tim Wong (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: