Steps to reproduce

1. Open a content app
2. Import attached bootstrap file into a folder
3. Click Publish recursive

Expected results

Content is published in acceptable time (minutes, depending)

Actual results

Publication takes hours, PostgreSQL might suffer from MAGNOLIA-8760 (to validate with other database).

Workaround

Decorate the app with:

subApps: 
  browser: 
    actions: 
      activateRecursive: 
        params: 
          itemTypes: nt:base

This might be not only a workaround but a proper way to publish huge amount of items.
This is applicable for content with total size in MB (the size of exported items).
This might be not applicable for binary content (e.g. assets, the size of exported items in GB).
This might not applicable for workflow (although we haven't received such use case), see the next section.

Development notes

PublicationCommand might do this with a configurable threshold parameter if needed e.g.

Recursive Publishing 1000 items which is above the threshold of 100, packing all nodes to reduce the amount of HTTP transactions.

If there is a use case including workflow

• it's not possible to use this approach as workflow creates separate versions for each node so it's not possible to export a parent node including children.
• we would need to create a wrapper which would collect these different versions so by exporting parent we would be exporting also children but redirecting to their proper versions.