Chuyển đến nội dung chính

[PERFORMANCE] Adobe WEM/CQ performance tuning

Adobe WEM/CQ performance tuning
Contents
Main documentation you should consult first:

Caching-related configurations

CRX Bundle cache

CRX caches bundles, consisting of a node with all its properties. This is used by all bundle-based Persistence Managers. The default size of BundleCache is 8 MB. If this is too small it can cause an excessive number of read-accesses to the underlying persistence layer.
Set the bundleCacheSize to something larger than the default. See more here: http://dev.day.com/docs/en/cq/current/deploying/performance.html#CRX%20Bundle%20Cache


CRX Search index handler (Lucene) cache

This Search configuration controls the size of the document number cache for Lucene indexes, which maps UUIDs to Lucene document numbers. Consider increasing this cache size as described in the links below.
See more here:


Tar PM index cache

To enable caching of the tar PM index (for TarPM optimization process), set value for indexinMemory to “true” for the TarPersistanceManager.

The indexInMemory configuration option causes the TarPM to buffer *all* index files entirely in memory. This can significantly boost performance, but be aware of the tradeoff: a significant RAM cost.
See more here:
To learn more about the Tar Persistence Manager, see:
Index Merge
Index merge will free up disk space and also speed up reading from the repository.
If many entries are stored in the tar files, the number of index files may grow. The index files are automatically merged before and after the scheduled Tar PM optimization. However, if you need to manually reduce the number of index files at other times, you can merge these index files using the CRX Console. See: http://dev.day.com/docs/en/crx/current/administering/persistence_managers.html#Manually Merging Tar Index Files


Scalability

Regarding CQ/CRX itself, the only known limitation that might affect performance directly are flat hierarchies. This means that you should avoid having content structures with thousands of nodes on the same level in the hierarchy. Source: http://dev.day.com/content/kb/home/Crx/CrxFAQ/CrxLimitation.html

Maintenance

Optimizing Tar Files (for Tar Persistence Manager)

As data is never overwritten in a tar file, the disk usage increases even when only updating existing data. A (typically) daily optimization routine runs to maintain these files, in which the Tar Persistence Manager copies data that is still used from old tar files into new tar files, and deletes the old tar files that contain only old or redundant data.
If the optimization routine is stopped mid-stream before it is finished completely, then the next time it is started it will continue from where it left off (i.e., it doesn't start from the beginning).


Data Store Garbage Collection

The data store can be used to store large binary values. Normally all JCR node and property data is stored in a persistence manager, but for large binaries such as files special treatment can improve performance and reduce disk usage.
The data store never deletes entries except when running data store garbage collection.
Execute garbage collection to remove any unused files in the Data Store. CRX supports the Jackrabbit data store. See http://wiki.apache.org/jackrabbit/DataStore

More here:






Find more resources about Adobe CQ5 / WEM here:


Nhận xét

Đăng nhận xét

Bài đăng phổ biến từ blog này

[Query Builder] Advanced Search

Using the Advanced Search When using a list, select from the 'Build list using' options 'Advanced Search.' This will open a new tab in the list window with one text box labeled: 'Querybuilder Predicate Notation.' This is asking for a few lines of code to define search parameters. Example Code - With Explanations of Results Searching for Pages type=cq:Page property=jcr:content/jcr:title property.value=Places 'type' defines what sort of object you'll be searching for (it's usually a page). 'property' defines what property of the object you'll be filtering by; in this case, its by the title. 'property.value' defines your search term. So this search would be searching all PAGES with the TITLE of PLACES. So it would find every page titled Places. *IMPORTANT* Searches by title ARE case-sensitive, so 'Places' is not the same as 'places'. type=cq:Page path=/cq/sandbox property=jcr:cont...
Đăng nhận xét
Đọc thêm

[CQ6-SYSTEM] MAINTAINING THE REPOSITORY - Reduce repository size (cleanup repository)

Compacting Tar Files As data is never overwritten in a tar file, the disk usage increases even when only updating existing data. To make up for the growing size of the repository, AEM employs a garbage collection mechanism called Tar Compaction. The mechanism will reclaim disk space by removing obsolete data from the repository. Revision Clean Up By default, tar file compaction is automatically run each night between 2 am and 5 am. The automatic compaction can be triggered manually in the Operations Dashboard via a maintenance job called Revision Clean Up. To start Revision Clean Up you need to: Go to the AEM Welcome Screen. In the main AEM window, go to Tools - Operations - Dashboard - Maintenance or directly browse to http://localhost:4502/libs/granite/operations/content/maintenance.html Click on Daily Maintenance Window. Hover over the Revision Clean Up window and press the Start button. The icon will turn orange to indicate that the Revision Clean Up ...
Đăng nhận xét
Đọc thêm