[PUBLISHING-69] Publishing large objects consumes lots of resources when using Java 11 Created: 04/Dec/19  Updated: 04/Apr/23  Resolved: 07/Jan/20

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: 1.1.3
Fix Version/s: 1.1.4

Type: Bug Priority: Major
Reporter: Richard Gange Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: 61, java11, performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causality
is causing PUBLISHING-80 Latest release depends on maintenance... Closed
dependency
depends upon MAGNOLIA-7702 Export of large files fails on Java 1... Closed
relation
is related to PUBLISHING-75 Add runtime dependency to SAX library... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Support
Sprint: SPA Editor 13, SPA Editor 14
Story Points: 3
Team: Nucleus

 Description   

To reproduce the issue:

  1. run Magnolia bundle (6.1.3) . on Java 8 to publish assets (a few Gigabytes) . --> worked fine
  2. run the same bundle as above on Java 11 and it takes so long (hours) for publishing big size images

Notes from customer:

In our production system we have a critical issue. Currently, we have uploaded app images with a total size of ~12GB in assets.

When publishing even a single image, almost every time the instance will utilise the CPU to 100% which cause timeout to all other process (e.g. restful calls from clients) and therefore abnormal functioning of the system.

Workaround
Downgrade (if possible) from Magnolia v6.1.3 to v6.1.2 and images publication works good with Java 11.



 Comments   
Comment by Richard Gange [ 04/Dec/19 ]

This can be a blocker for any customer that has written Java 11 specific code. To use Java 11 you must stick with Magnolia 6.1.2. Otherwise use a different version of Java.

Generated at Mon Feb 12 10:35:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.