Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Custom Image Rendition servlet vs DAM Update Assets workflow Renditons

Avatar

Avatar
Validate 1
Level 1
avinasht7298469
Level 1

Likes

3 likes

Total Posts

4 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 1
avinasht7298469
Level 1

Likes

3 likes

Total Posts

4 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
avinasht7298469
Level 1

11-12-2017

In AEM ,I have seen project where we have used custom image rendition servlet (Generating rendition on fly) or DAM update Asset workflow.

If we are using custom image rendition servlet ,It has certain benefits(Named Transform Image Servlet ).

1. can create new image rendition on the fly based upon configuration .

2. Save space in AEM .

3. Also performance vice ,the image are cached in dispatcher for both author and publisher ,so only rendition creation only for the first time.

Limitation

1.New image rendition need to created if cache is cleared.

if we are using DAM update Asset workflow, It has certain limitation.and benefits.

Limitation

1. whenever author upload image this workflow trigger new rendition are created for every image and at at time we dont need all rendition.

2 if we are migrating large asset ,it is again bottleneck.

3. take additional space in author and publisher as well for all images

Benefits

1. new image rendition is not created every time but just once .

Question:

If I evaluate from above reasoning i believe that image rendition servlet is more useful in term of saving space and load on author and publish server .

Is the above approach  is recommendation/best practice from adobe or if someone have completely different perspective.

View Entire Topic

Avatar

Avatar
Springboard
Level 1
rakz_r
Level 1

Like

1 like

Total Posts

7 posts

Correct Reply

1 solution
Top badges earned
Springboard
Establish
Give Back
Ignite 1
Validate 1
View profile

Avatar
Springboard
Level 1
rakz_r
Level 1

Like

1 like

Total Posts

7 posts

Correct Reply

1 solution
Top badges earned
Springboard
Establish
Give Back
Ignite 1
Validate 1
View profile
rakz_r
Level 1

12-12-2017

Performance wise:

  1. An Image on the Fly:
    • If there are multiple images on a page and all are images on the fly these request hitting the publisher will certainly have an impact. Each request gets the response from the Servlet and its cached in the dispatcher for the subsequent request.
    • If the same image is used in multiple pages, each page may have it own image URL.
    • For any image update: Clearing those image you may have to activate the parent node(either the dam asset or page)
    • Doesn't consume space in the publisher
  2. Renditions Based:
    • The renditions are a readily available resource in the publisher in the DAM and can be served much faster if the same scenario is applied.
    • One Image will have the same URL for all the pages referenced on the site.
    • For any image update: Author can update one rendition or update an original image in the DAM and clears the dispatcher respectively
    • Consumes spaces in the publisher.

You can create a sample page with two different implementations and check the load time of the page for the first time and subsequent times to record the performance metrics. Take decisions based on it.

I could say it depends on the requirement.

If showing images in the multimedia section like displaying photos in an album rendition is better.

If displaying smaller thumbnails rendition size which is not going to be used anywhere on the site you can use adaptive image/named transform image. Instead of having that thumbnails rendition size to be stored by the author and publish's DAM.