Once migration is complete, the performance when accessing data in the target file-system is that of a normal HNAS file system.
During the virtualization phase the performance is governed by a number of factors, including the capability of the LNAS, and the network connection to it. In addition the HNAS has to track the state of the objects in the association and send all modifying and IO operations to the LNAS. The result of this is that performance compared to a normal HNAS file system is significantly degraded. This is particularly the case when many (several hundred) parallel client operations are made on the virtualized data at the exact same time. If the desired use case of the feature is likely to include this type of load, it may be prudent to postpone widespread client access until after virtualization is complete, and migration is well underway.