eZ Publish Asynchronous Content Publishing

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 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

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

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

eZ Publish Asynchronous Content Publishing

by Bertrand Dunogier on Jan 28, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

2 Embeds 41

Statistics

eZ Publish Asynchronous Content Publishing — Presentation Transcript

http://share.ez.no	40
http://paper.li	1