Performance implications

Large object writes can get delayed
Standard and protected vault mirrors favor availability (returning an object)
For GET requests where the faster site results in object not found, the system always waits for the slower site. The requested object may have only been written to one vault or have been deleted during from one vault during a network partition and not yet be synchronized. Thus, rather than returning NOT FOUND if the faster responding site does not have the requested object, the system waits to see what the slower sites response is before passing along a response to the client system.

Parent topic: Deploying vault mirrors and protected mirrors