Uploaded image for project: 'Migration 4.4 to 4.5 (closed)'
  1. Migration 4.4 to 4.5 (closed)
  2. MGNLMIGRATION-234

Optimize performance for large projects

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.2.2
    • Component/s: None
    • Labels:
      None

      Description

      The module works with session based saving. The more nodes to migrate, the slower it is. This is an exponential function. It makes migrating large sets of nodes a neverending job. We should think about workspace based saving/export/import/...

      F.e. having about 10 thousands pages and focusing on "update node type" task, the migration is able to perform about 20 thousands of node types changes in first hour, 15 thousands in second hour, 10 thousands in third hour, ..., 3 thousands in 18th hour, etc. Such job would need about 3 days, which can't be acceptable. The linked migration.log is a good reference (covers less then a day), it was running on 8GB RAM and 2 CPUs.

        Checklists

        Acceptance criteria

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                rkovarik Roman Kovařík
                Reporter:
                zdenekskodik Zdenek Skodik
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:
                  Date of First Response: