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

Lots of content - AEM Author performance issues

Avatar

Avatar
Validate 1
Level 2
surenk
Level 2

Likes

9 likes

Total Posts

48 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Validate 1
Level 2
surenk
Level 2

Likes

9 likes

Total Posts

48 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back
View profile
surenk
Level 2

21-10-2019

One of our customer has migrated a lot of content (assets and pages)... they have about 1.5 million assets and about 4 million site pages. Part of the sites are generated by XML Add-on.

Problem:

With this much load obviously Author (AEM 6.4) is slow for authoring. And sometimes crashes.

Solutions:

  • The server where AEM author is running has been upgraded to have a lot of resources (94 core CPU and 384GB memory).. this maybe not be best solution but did not help a lot.
  • Going through all the AEM systems configuration (workflows, any orphan process, etc.)
    • Using ACS Commons' Bulk Workflow tool.
  • Review an Elastic search index configured that runs weekly
  • Following offline-compaction and other suggested per the AEM 6.x Maintenance Guide

Usually what can be done with repository of such huge sizes?

View Entire Topic

Avatar

Avatar
Validate 1
Level 2
Santhi_Swaroop
Level 2

Likes

16 likes

Total Posts

28 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile

Avatar
Validate 1
Level 2
Santhi_Swaroop
Level 2

Likes

16 likes

Total Posts

28 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 3
Ignite 1
Give Back 5
Give Back 3
View profile
Santhi_Swaroop
Level 2

22-10-2019

Try to shard the content/sites to two different authors and publish to same publish instances so that you can minimize the load by 50%