Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
EZ Asynchronous Publishing A new feature in Matterhorn
Presentation A simple & pragmatic workaround for a complex problem A heavy flow of content publishing can lead to  LOCK ti...
Under the hood Quick dive into the system's guts Settings:  content.ini Feature is  disabled by default  (BC) The  queue s...
Better user feedback Cronjob based workflows  won't silently interrupt.  Custom feedback  is possible ! After publishing, ...
Upcoming SlideShare
Loading in …5
×

eZ Publish Asynchronous Content Publishing

23,638 views

Published on

A 10 minutes flash talk given at the eZ Systems winter conference 2011 in Nice about the new eZ Publish Asynchronous Content Publishing feature.

Published in: Technology
  • Be the first to comment

eZ Publish Asynchronous Content Publishing

  1. 1. EZ Asynchronous Publishing A new feature in Matterhorn
  2. 2. Presentation A simple & pragmatic workaround for a complex problem A heavy flow of content publishing can lead to LOCK timeouts Lock wait timeout exceeded; try restarting transaction. Query: UPDATE ezcontentobject_tree SET modified_subnode=1291901964 WHERE node_id IN The transaction is too big It can't easily be reduced Let's reverse the issue , and limit what we ask to the DB Send publishing operations to a centralized, controlled queue Have the queue process publishing operations in background
  3. 3. Under the hood Quick dive into the system's guts Settings: content.ini Feature is disabled by default (BC) The queue size is configured here Publishing done through a real system daemon with forks Minimal memory usage : one process publishes one object, and dies User interaction is done through content/queued.tpl , a new view/template: This template updates itself using ezjscore/ AJAX It is fully overrideable (class, section, id, etc) Feature is only enabled for content/edit
  4. 4. Better user feedback Cronjob based workflows won't silently interrupt. Custom feedback is possible ! After publishing, one can access the (newly) published object No more long waiting time when publishing Queued objects are visible as pending items Benefits There are extra bonuses ! 01/27/11

×