[MGNLDAM-768] Pre cache image variants on save Created: 15/Nov/18  Updated: 17/Mar/21  Resolved: 17/Mar/21

Status: Closed
Project: Magnolia DAM Module
Component/s: DAM App
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Jan Haderka Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLIMG-213 Asset upload in ZIP file to DAM may c... 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)
Release notes required:
Yes
Date of First Response:
Epic Link: Imaging performance

 Description   

While encountering MGNLIMG-210 it turned out that one possible way to counter uncertainty and spikes created by generating too many variants concurrently would be to pre-generate and cache said asset variants, already known to be requested by action bar or workbench upon save of dialog and return to browse subapp, while saving the asset.

Acceptance criteria:

  • make pre-generation of variants optional
  • do not fail to save asset even when generation fails
  • generate variants only for images


 Comments   
Comment by Jan Haderka [ 15/Nov/18 ]

Require release notes to explain that precaching is enabled by default now and how to disable it or what the consequences might be.

Comment by Jan Haderka [ 17/Mar/21 ]

Closing in favour of externalizing image processing

Generated at Mon Feb 12 05:03:05 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.