Having a CQ “dispatcher” configured between a CQ “publish” instance and your users will provide dramatic (about 85%) performance improvements. For example, in the case of the Geometrixx sample website that all CQ instances come packaged with (at /content/geometrixx/en.html), invoking the page directly from the “publish” instance takes about 12.4 seconds while invoking it from the Dispatcher takes only 1.8 seconds.
Digital Asset Management (DAM)
Having a CQ “dispatcher” configured between a CQ “publish” instance and your users will provide about a 15% performance improvement for a typical digital asset such as an image.
CQ’s Dispatcher is an HTTP Server Plugin, meaning it extends the functionality of popular HTTP servers such as Apache HTTP server and Microsoft IIS. It’s built and packaged as a .so (“shared object” in Unix) or .dll (dynamically linked library in Windows). For example, disp_apache2.2.dll is the CQ Dispatcher for Apache version 2.2 for Windows.
To quantify the incremental performance benefit of having a Dispatcher, I ran one CQ “author” and one “publish” instance on a Dell Dimension 720 workstation running Windows 7 Home Edition 64-bit. The Java environment was Oracle HotSpot 1.6.0_35 64-bit.
Apache HTTP Server 2.2 (32-bit) ran on the same Windows instance with Dispatcher version 4.1.2 Apache in-memory caching module mod_mem_cache was enabled (100 MB) and configure to cache documents up to 10 MB in size. See httpd.conf and dispatcher.any
Using Opera 12.02 on the same Windows instance, a 9.2 MB PDF file in CQ DAM was repeatedly (manually) requested ten times. Performance details were measured using Opera’s built-in diagnostics tool Dragonfly - documented in Excel spreadsheet format here. See screenshot below:
No comments:
Post a Comment
If you have any doubts or questions, please let us know.