Optimize your 6.4 AEM Assets Implementation
•Télécharger en tant que PPTX, PDF•
1 j'aime•394 vues
Deriving ROI with your investment in AEM Assets Implementations start with selecting the right deployment models for your use cases. Once the right deployment model is executed, the next consideration is to optimize the implementation for optimal performance. Optimizing your AEM Assets Implementations comprehensively, includes introspecting how your Assets are stored, transferred, processed, used, maintained and served to your customers. Delivering a world class digital experience starts with an optimized Digital Assets Management. This session gives you insights into how you can get the most of your Assets implementation while maintaining optimal performance.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Optimize your 6.4 AEM Assets Implementation
Similaire à Optimize your 6.4 AEM Assets Implementation (20)
Plus de Evolve The Adobe Digital Marketing Community
Plus de Evolve The Adobe Digital Marketing Community (20)
Dernier
Dernier (20)
Optimize your 6.4 AEM Assets Implementation
- 1. #evolve18August 17th 2018 Optimizing your 6.4 AEM Assets Implementation Ameeth Palla | Manager, AEM Customer Experience @ Adobe
- 2. #evolve18 2 MENU Deployment Options – Store Replication – Transfer Workflows – Process Optimizations – Tune Maintenance AEM Support Overview AEM – Creative Cloud Integration
- 4. #evolve18 4 Apache Oak APACHE OAK – NODE STORAGE
- 5. #evolve18 5 OPTIMIZE AEM ARCHITECTURE Key points to consider: • External Datastore (FileDS/S3/Azure) • SegmentMK (TarMK) • Better Performance • Within Adobe Stack • Cold Standby • DocumentMK (MongoMK) • High Availability • Horizontal Scalability - https://helpx.adobe.com/experience-manager/6-4/sites/deploying/using/data-store-config.html - https://helpx.adobe.com/experience-manager/6-4/sites/deploying/using/recommended-deploys.html
- 6. #evolve18 6 • Using incorrect deployment Models/Topology • Not using an External Datastore • No proper backup strategy • Repository corruption COMMON ISSUES
- 8. #evolve18 8 WORKFLOWS • Transient Workflows • Use when: workflow history is not needed • Benefits • Better performance • Smaller Repository size • Smaller Maintenance time - https://helpx.adobe.com/experience-manager/6-4/sites/developing/using/workflows- models.html#CreatingaTransientWorkflow - https://helpx.adobe.com/experience-manager/6-4/assets/using/performance-tuning- guidelines.html#Workflows
- 9. #evolve18 9 WORKFLOWS • Workflow Offloading • Useful for resource intensive processing • Video transcoding • High volume • Benefits • Better performance • Parallel processing (1 Author : many workers) • Pitfalls to avoid • Replication overhead – use Binary-less replication • Make DAMUpdateAsset workflow non- transient. - https://helpx.adobe.com/experience-manager/6-4/assets/using/assets-offloading- best-practices.html - https://helpx.adobe.com/experience-manager/6-4/assets/using/performance- tuning-guidelines.html#Workflows
- 10. #evolve18 10 • Lack of proper maintenance – workflow purging • Too many versions • DAM Update Asset workflow – should not be transient if using Offloading COMMON ISSUES
- 12. #evolve18 12 BINARY LESS REPLICATION • Shared Datastore • Reduce transport overhead. (Offloading and/or Publish) - https://helpx.adobe.com/experience-manager/6-4/sites/deploying/using/data-store-config.html#AmazonS3DataStore -> Configuring binaryless replication with Amazon S3
- 13. #evolve18 13 • Reduce replication overhead on Author • Author -> Publish -> Publish CHAIN REPLICATION - https://helpx.adobe.com/experience-manager/6-4/assets/using/performance-tuning-guidelines.html#Replication
- 14. #evolve18 14 • Replication agents are not configured correctly. • System is low on resources • Replication is happening as part of a custom workflow – dependency on workflow processing • Configuring proxy server between Author/Publish – Enterprise security practices COMMON ISSUES
- 16. #evolve18 16 • Java Temp Folder • Benefit • Improve Asset Upload times • What to use • High performance storage (SSD) • RAM drive • Ephemeral (Amazon EC2) • Network Optimization • HTTPS – Avoid sniffers • Wired Connections for Large Asset uploads • Bandwidth OPTIMIZATIONS - https://helpx.adobe.com/experience- manager/6-4/assets/using/performance- tuning-guidelines.html#JavaConfiguration - https://helpx.adobe.com/experience- manager/6-4/assets/using/performance- tuning- guidelines.html#NetworkOptimization
- 17. #evolve18 17 • Index definitions • Precise • Use Nodetypes – To allow multiple queries to make use of same index • Lucene or Property Index? – Use Lucene unless explicit need of property index is determined OPTIMIZATIONS Property Indexes (Sync) Lucene Indexes (Async) Updates as soon as data is persisted Updates per defined schedule once data is persisted Always in sync with latest repo changes Runs as a background job every 5 seconds Failure causes exception on save On error, tries again Affects save operation Does not affect save operation
- 18. #evolve18 • JVM tuning for better Index performance • What to use • Set optimal JVM parameters for optimal Index performance. Use latest supported Java version. • Sample config shown below. Test for every use case. • Tuning Sling Job Queue: • When to use • Bulk uploading of large Assets • What to use • configMgr - > org.apache.sling.event.jobs.QueueConfiguration and set queue.maxparallel to a value representing 50% of the CPU cores of the server hosting your AEM instance XX:+UseConcMarkSweepGC = Enable Concurrent Mark Sweep (CMS) Collector -Doak.queryLimitInMemory=500000 -Doak.queryLimitReads=100000 -Dupdate.limit=250000 -Doak.fastQuerySize=true 18 OPTIMIZATIONS
- 19. #evolve18 19 • Disable Lucene Text extraction (tika) • When • Content search within Assets is not required • Benefits • Improves index performance • Reduces overall index size • Disable Sub-Asset Generation • When • Separate Pages with PDF’s/Word documents not needed • Benefits • Reduces disk space • Reduces Processing, Versioning & maintenance needs • Conserves resources & improves Performance OPTIMIZATIONS - https://helpx.adobe.com/experience- manager/6-4/assets/using/performance- tuning-guidelines.html#SearchIndexes - https://helpx.adobe.com/experience- manager/kb/Disable-binary-text-extraction- to-optimize-Lucene-indexing-AEM.html - https://helpx.adobe.com/experience- manager/6-4/assets/using/performance- tuning-guidelines.html#Workflows
- 20. #evolve18 20 • Adobe’s Image Transcoding Library • Core Image handling functions (Encoding, Transcoding, Image resizing, etc) • Advantages over other 3rd party libs (performance, scalability and quality) • PDF Rasterizer • Accurate Output • Selective & Quality thumbnails • Faster processing - Less memory usage Both supported in AEM 6.3 and 6.4 Both compatible with Offloading and Transient Workflow https://helpx.adobe.com/experience-manager/6-3/assets/using/imaging-transcoding-library.html https://helpx.adobe.com/experience-manager/6-3/assets/using/aem-pdf-rasterizer.html OPTIMIZATIONS
- 21. #evolve18 21 • Chunk Uploads : https://helpx.adobe.com/experience-manager/6-4/assets/using/managing-assets-touch-ui.html • Workflow retries : Change defaults and set a low value • Customize the DAM Update Asset Workflow : remove unrequired workflow steps. OPTIMIZATIONS
- 22. #evolve18 22 Indexing related Issues • Incorrect indexes • Indexing more content than required • Missing Index for the query causes repository traversal Workflows related Issues • Not configuring Workflow retries • Incorrect configuration for Offloading/Binary-less replication • Transient workflows configured when auditing is needed. • Performance issues with large batch uploads of Assets COMMON ISSUES
- 24. #evolve1824 AEM MAINTENANCE Maintenance Task Tar MongoDB Default Window Version Purge Yes Yes Configurable Workflow Purge Yes Yes Weekly Audit Log Purge Yes Yes Configurable Data Store GC Yes Yes Weekly Online Revision Clean-Up Yes No Daily Offline Revision Clean-Up (aka Tar Compaction - 6.2 and older) Yes No Weekly Log rotation Yes Yes Daily https://helpx.adobe.com/experience-manager/kb/AEM6-Maintenance-Guide.html
- 25. #evolve1825 AEM 6.4 MAINTENANCE - https://helpx.adobe.com/experience-manager/6-4/sites/deploying/using/revision-cleanup.html - https://helpx.adobe.com/experience-manager/6-4/release-notes/wcm-platform.html Maintenance Task Tar MongoDB Maintenance Window Tail Compaction Yes No Daily Lucene File Cleanup Yes Yes Configurable Project Purge Yes Yes Configurable Ad-hoc tasks purge Yes Yes Configurable Continuous Revision GC No Yes Every 5s Oak-run reindexing Yes Yes As needed • Enhanced logging • Version purge and Audit purge stop at end of maintenance window
- 27. #evolve18 27 • Links Creative Cloud for enterprise with AEM • Makes collaboration between creatives and marketers easy • Native integration of AEM within • Photoshop • Illustrator • InDesign • *Limited Release to CC for Enterprise and AEM Assets customers ADOBE ASSET LINK
- 29. #evolve18 29 TAKEAWAYS • Use an External Datastore • Plan and Test your Asset Upload Strategy • Tune configurations to suit your use case for optimal performance • Have a robust maintenance and system monitoring plan • Upgrade to the latest version of AEM (SP & CFP) • TEST comprehensively before moving to production
- 31. #evolve18 31 • Log tickets via AEM Support Portal – Daycare • Call support @ 1-800-497-0335 (US & Canada) for any urgent P1/P2 issues after logging the ticket. • Use dmaESCALATIONS@adobe.com to escalate any ticket. • AEM Support landing page: https://helpx.adobe.com/support/experience- manager/6-4.html • Common Critical AEM issues: https://helpx.adobe.com/experience- manager/kb/common-critical-AEM-issues.html • Customer Care Office Hours: https://helpx.adobe.com/customer-care-office- hours.html • Experience League: https://landing.adobe.com/experience-league/ ADOBE AEM SUPPORT – INFO & LINKS TO BOOKMARK