Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-24870

Create a know limitation specifying the maximum size of a package to be importaed with ezpm

    Details

      Description

      ezpm script won't work if you try to import a big package (in my case, I tested it with 11Gb) using the following command

      php ezpublish/console ezpublish:legacy:script --siteaccess=my_sa ezpm.php import my_package-1.0-1.ezpkg
      

      I checked ezpackage.php and it seems the error happens when it loads the file into a new DOMDocument.
      According to what I searched in the Web, this kind of object may not work properly if it exceeds the available memory (it's a really large package, with a really large XML File).

      That said, it's important to add a known limitation with the maximum allowed size for a package to be imported with ezpm. Also, it would be important to have this warn added to the package creation page.

        Activity

        Hide
        Joao Inacio (Inactive) added a comment -

        After analysis of large package(s) and memory consumption, it was found that the memory usage does grow somewhat with the size of the `package.xml` file (which in turn grows with the number of content objects/classes//files/etc).
        However, memory usage is almost negligible - Initial usage is roughly 64MB for the script, with a few MB more allowing for hundreds or thousands of content entries.

        Given the eZ Publish memory requirements of 256MB minimum, many thousands of objects can be imported with ezpm regardless of the final package file size (which depends heavily on the existence of binary files/media/etc).

        In sum:
        The maximum size of a package to be imported with ezpm should depend on server hardware, within the usual and reasonable disk / memory / processor / time constraints, so no special documentation is required.

        Show
        Joao Inacio (Inactive) added a comment - After analysis of large package(s) and memory consumption, it was found that the memory usage does grow somewhat with the size of the `package.xml` file (which in turn grows with the number of content objects/classes//files/etc). However, memory usage is almost negligible - Initial usage is roughly 64MB for the script, with a few MB more allowing for hundreds or thousands of content entries. Given the eZ Publish memory requirements of 256MB minimum, many thousands of objects can be imported with ezpm regardless of the final package file size (which depends heavily on the existence of binary files/media/etc). In sum: The maximum size of a package to be imported with ezpm should depend on server hardware, within the usual and reasonable disk / memory / processor / time constraints, so no special documentation is required.

          People

          • Assignee:
            Unassigned
            Reporter:
            Eduardo Fernandes (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: