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

Improve the performance of the page tree expansion on the Move Page dialog

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • Tested on Confluence 5.9.3 by trying to move a parent page with 3 levels of nested children pages that each has 400-1500 children pages
    • 4
    • 11
    • 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.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Summary

      Page tree expansion process during page move attempt for pages that have a large number of child pages takes a long time to display all of the children pages should Browse function is used from Move Page dialog feature.

      Steps to Reproduce

      1. Attempt to move a parent page with a large number of child pages (200-1000++ child pages) via ... >> Move >> Browse on the page that you're about to move.
      2. Watch the spinning wheel going for a long time (approx. 15-50 seconds) while Confluence tries to finished the Page Tree expansion process.

        1. Screen Shot 2016-01-12 at 4.03.41 PM.png
          Screen Shot 2016-01-12 at 4.03.41 PM.png
          80 kB

            [CONFSERVER-40454] Improve the performance of the page tree expansion on the Move Page dialog

            Henry Auffahrt added a comment -

            We have a similar issue trying to move pages.

            Our Version is: Atlassian Confluence 6.13.4 (Cluster node: 36884286) (With Multi-node)

            Henry Auffahrt added a comment - We have a similar issue trying to move pages. Our Version is:  Atlassian Confluence  6.13.4 (Cluster node: 36884286) (With Multi-node)

            Paula Dasch added a comment -

            Should not be a suggestion, but a bug.

             

            Paula Dasch added a comment - Should not be a suggestion, but a bug.  

            Paula Dasch added a comment -

            6.5.2 seems affected, too

            Paula Dasch added a comment - 6.5.2 seems affected, too

            bolmstrand added a comment -

            Hi,

            I don't mind the time it takes to do this, but there should be more info/warnings displayed as the "actual" moving is ongoing. Really bad and unexpected things can happen, e.g this:

            • I created a new empty page and moved a large subtree as a child to this new page - about 2500 pages
              • seemed fine within space-tools section so I went to check the "real" page tree
            • But, no change. My new page still had no children
              • thought first that I forgot to press save, so tried again but no change in real tree
            • Finally decided to delete the new page and go find out what I did wrong...
              • the regular warning appeared when I deleted the page, no mention of any child-pages that were going to be deleted. 
              • as expected, so I pressed ok. That single delete took time for some reason...
            • Came back after lunch and realised everything was gone!
              • my new empty page but also the entire subtree with my 2500 pages!

            I guess the moving of pages was in fact going on but wasn't finished when I deleted my new page, so no warning that I was about to delete all those pages. Luckily, those pages were freshly imported and could be re-imported, but otherwise it would have been a pain to restore them one-by-one.

             

             

            bolmstrand added a comment - Hi, I don't mind the time it takes to do this, but there should be more info/warnings displayed as the "actual" moving is ongoing. Really bad and unexpected things can happen, e.g this: I created a new empty page and moved a large subtree as a child to this new page - about 2500 pages seemed fine within space-tools section so I went to check the "real" page tree But, no change. My new page still had no children thought first that I forgot to press save, so tried again but no change in real tree Finally decided to delete the new page and go find out what I did wrong... the regular warning appeared when I deleted the page, no mention of any child-pages that were going to be deleted.  as expected, so I pressed ok. That single delete took time for some reason... Came back after lunch and realised everything was gone! my new empty page but also the entire subtree with my 2500 pages! I guess the moving of pages was in fact going on but wasn't finished when I deleted my new page, so no warning that I was about to delete all those pages. Luckily, those pages were freshly imported and could be re-imported, but otherwise it would have been a pain to restore them one-by-one.    

            Petro Semeniuk (Inactive) added a comment -

            Hey guys, just to be clear.

            Before we fixed page move in 5.8.18/5.9 moving couple hundred pages would tae few hours/overnight and could easy bring large instances down.

            It was fixed and seeing description "spinning wheel going for a long time (approx. 15-50 seconds)" is actually quite fast.

            Three weeks of eng effort was spent to achieve that.

            If you want to push page move performance event further you must have buy-in from PMs.

            I can't possibly current behaviour as a bug.

            For customers who want to move 10K pages - they could move subtrees. It's acceptable workaround.

            Petro Semeniuk (Inactive) added a comment - Hey guys, just to be clear. Before we fixed page move in 5.8.18/5.9 moving couple hundred pages would tae few hours/overnight and could easy bring large instances down. It was fixed and seeing description "spinning wheel going for a long time (approx. 15-50 seconds)" is actually quite fast. Three weeks of eng effort was spent to achieve that. If you want to push page move performance event further you must have buy-in from PMs. I can't possibly current behaviour as a bug. For customers who want to move 10K pages - they could move subtrees. It's acceptable workaround.

              Unassigned Unassigned
              lrura Lauretha Rura
              Votes:
              14 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated: