Just to add to what wabe is saying, I think Vue does a lot of calculation during the save scene process. For example, populate a large (6000x6000) procedural terrain with an ecosystem. The file size might be around a few hundred mb. But you'll notice that even if saved locally it takes quite a long time to save a file of that size, far longer than you would expect if it was just writing to the disk. This is because I believe Vue is also calculating/saving out the location/coordinates for each ecosystem object. From what I've observed this is done as it is saved, and I'm assuming the data is appended to the vue scene during the process. Now, do this over a network and you've probably got relatively small packets being sent. As such each one is not taking advantage of the full bandwidth of your network, but it is being slowed down as opposed to writing to a local disk. I also believe it's probably done this way to save memory. As if you had to pre-calculate all this stuff before the save you could quite possibly run out of memory then. Please note this is just my assumptions on the matter, but I do know for a fact that Vue reads in each ecosystem coordinate when you load a scene, which can be far longer than the corresponding scene save, so it's safe to say that it is also saving each coordinate. Hope that helps.