Perform concurrent position updates only after a portfolio node's entire set of positions has been read in and merged,
and barrier sync position update tasks before proceeding to next node's positions. This approach limits exploitable
concurrency but is currently necessary to avoid issues with concurrent update() invocations; additional concurrency
can be extracted with some more work.