shotgunsoftware/shotgunEvents — Issue #19: Multiple Events causing redundant event updates
Author: cmihaly
Created: 2012-01-09 07:03:04+00:00
State: open

An issue we have with our current trigger sw, and I think this has too, is that we have some triggers that based on certain different actions (status changes, task on the object status changes, task assignee changes, etc) go through and recompute a field on the shot. The update is a bit expensive in a few seconds. The problem is, creating a shot, or certain API operations, cause many of these fields to update on the same operations. Our event loop recomputes the field for each field change, even though it was actually one operation. Because it is fairly expensive update operation, this causes our event triggers to fall behind.

I was wondering if anyone has dealt with this. This may actually be more an attribute of the plugin. One idea was to change the plugin to basically queue the events uniquely per entity in a queue, and have a separate process read the queue and do the operations. If multiple items come in, then they will all be handled once.