When we talk to project teams about Collaboration for Revit, a common thread emerges where everyone agrees -> there’s no such thing as an operation that can be too fast. We agree, and are constantly optimizing the service to deliver a better performance experience. With our most recent update to the service – C4R 2015.5 or C4R 2016.0 – we implemented a new technique to deliver the further optimized experience.
As many of you know, transactions between the Revit application and the place of record for the model (aka Central Model) happen in the form of deltas, rather than pushing around the entire model, which can be quite large.
Based upon a number of factors, a single Sync With Central (SWC) operation is going to consist of a number of delta files to be processed by Revit. There will be inbound deltas consumed by the Reload Latest portion at the start of SWC (from other team members doing a SWC). There will be outbound deltas consumed by the central model based upon the changes of the current team member. Up until the latest release, we transferred these deltas between the Revit application one-at-a-time, or “in serial” as our developers call it.
Now, with the latest update, we have begun transferring these deltas in parallel, so the data is moving across the pipe faster, and the necessary data is available for processing on either side of the transaction quicker.
When we analyze the impact of this new process using real-world projects from customers like yourselves, we find some nice improvements to performance.
We on the product team are pretty excited about these improvements, and we hope that the teams using C4R enjoy the improved performance. It’s all part of our continued delivery of value to subscribers. Rest assured, we have a number of other improvements in the backlog, and we’ll be discussing them here Inside the Factory as they come.