Uploaded image for project: 'eZ Platform Enterprise Edition'
  1. eZ Platform Enterprise Edition
  2. EZEE-2865

Perfomance Issue with Serializer Configuration

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: High
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Page Builder
    • Labels:
      None

      Description

      The NonSharedSerializer creates new instances of the JMS Serializer for every serialization / deserialization call.

      The problem is that several hundred or thousands of calls can be made per request (e.g. when using loadContent() with a content object that has a page field.

      The JMS Serializer will reload the config file for every single call. This will create lots of Disk I/O and stall the CPU, especially when not using an SSD hard drive.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            r-hillebrand Roman Hillebrand
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: