Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.
APRIL 2015
NEXUM ACCELERATOR
For Magnolia CMS 5.3.x
2
ABOUT THE ACCELERATOR
 Provided as a Magnolia module
 Replaces Magnolia‘s DefaultRenderingEngine
 Caches the output r...
3
COMPATIBILITY & REQUIREMENTS
 Tested with Magnolia 5.3.x
 Works with Freemarker and JSP templates
 Works with Magnoli...
4
CONFIGURING CACHE BEHAVIOUR
 Install the Accelerator Module
 Magnolia‘s Cache filter will be deactivated, but it‘s eas...
5
AVAILABLE CACHE DIRECTIVES
 never
 Element is not cacheable
 always
 Just one variant of the element will be cached
...
6
AVAILABLE CACHE DIRECTIVES (CONTINUED)
 uri
 Caches a separate variant of the element for every request URI (page)
 c...
7
EXAMPLE (SCREENSHOT)
8
FURTHER EXAMPLES
 content-uri;user;
 Caches a separate variant for every content-URI (page/area) and user
(HTTP sessio...
9
ACCELERATOR APP
10
DEMO PAGE
11
CONTACT
Jörg Krähschütz
Unit-Direktor Transaktion
nexum AG
joerg.kraehschuetz@nexum.de
Nächste SlideShare
Wird geladen in …5
×

nexum Accelerator for Magnolia CMS: short presentation

800 Aufrufe

Veröffentlicht am

Mit der Realisierung eines neuen Accelerator-Moduls hilft die nexum allen Betreibern personalisierter, auf dem Magnolia CMS basierender Websites, die Leistungsfähigkeit zu steigern und die Last deutlich zu minimieren.

Veröffentlicht in: Software
  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

nexum Accelerator for Magnolia CMS: short presentation

  1. 1. APRIL 2015 NEXUM ACCELERATOR For Magnolia CMS 5.3.x
  2. 2. 2 ABOUT THE ACCELERATOR  Provided as a Magnolia module  Replaces Magnolia‘s DefaultRenderingEngine  Caches the output rendered by Magnolia‘s Renderers  Allows to cache each element (pages, areas, components) separately in several variants  Uses an in-memory LRU cache (cache size is configurable)  Provides two demo pages that illustrate cache behaviour  Adds an „Accelerator App“ to Magnolia‘s Admin Central to inspect cached variants and to flush the cache explicitly
  3. 3. 3 COMPATIBILITY & REQUIREMENTS  Tested with Magnolia 5.3.x  Works with Freemarker and JSP templates  Works with Magnolia‘s Freemarker and JSP tags, no new templating tags or template modifications needed  Requires Magnolia‘s Observation module to be installed in order to flush the cache on changes
  4. 4. 4 CONFIGURING CACHE BEHAVIOUR  Install the Accelerator Module  Magnolia‘s Cache filter will be deactivated, but it‘s easy to go back to or to disable the Accelerator  Add a parameters node to any page, area or component element in Magnolia‘s configuration workspace  Within this parameters node, add a property cacheDirectives  Specify a semi-colon separated list of cache directives in the cacheDirectives property  Default behaviour: if an element lacks any cache directives at all, the element won‘t be cached
  5. 5. 5 AVAILABLE CACHE DIRECTIVES  never  Element is not cacheable  always  Just one variant of the element will be cached  no-params=(param1,param2,...)  Prevents caching of the element if any of the listed request parameters appears in the request  user  Caches a separate variant of the element for every user (HTTP session)  locale  Caches a separate variant per request locale
  6. 6. 6 AVAILABLE CACHE DIRECTIVES (CONTINUED)  uri  Caches a separate variant of the element for every request URI (page)  content-uri  Caches a separate variant of the element for every content-URI (e.g. same element is used in different pages/areas)  timeout={N}  The cached variant of the element will be expired every N minutes  params=(param1,param2,...)  Caches a separate variant of the element for every value of the listed request parameters
  7. 7. 7 EXAMPLE (SCREENSHOT)
  8. 8. 8 FURTHER EXAMPLES  content-uri;user;  Caches a separate variant for every content-URI (page/area) and user (HTTP session)  content-uri;params=(firstname);no-params=(submit);  Caches a separate variant for every content-URI (page/area) and request parameter “firstname”; however, if a parameter “submit” appears in the request, caching of the element will be prevented  content-uri;timeout=5;  Caches a separate variant for every content-URI (page/area), but the cached variant will be expired every 5 minutes (x.05h, x.10h, x.15h, x.20h etc. pp.)
  9. 9. 9 ACCELERATOR APP
  10. 10. 10 DEMO PAGE
  11. 11. 11 CONTACT Jörg Krähschütz Unit-Direktor Transaktion nexum AG joerg.kraehschuetz@nexum.de

×