Buffer files locally for improved performance

[Viktor94]

I would like to see that my drawings files would be locally stored on my computer and then updated to the cloud in the background. As it is now saving a file, creating a new file, moving, renaming etc is painfully slow and significantly lowers my productivity.

It would also be good to have the local copy remain without having to turn on offline mode so that the software dont freeze as soon as the internet connection is lost. Basically i like to see it working similary to OneDrive.

[WyzeOwl]

Sadly, local storage will never be allowed simply because this will defeat the purpose and future revenue stream of Fusion. Cloud based storage is where this is all going after we all get the software performance to an acceptable level. Once there are enough users with too much invested in time, the free cloud storage will become a pay for space deal. The adage "nothing is free" holds true here just as much as everywhere else. Right now the fee we are all paying is data and intel. Once Fusion fledges - and it certainly will, the need for user input will diminish which is when storage fees will be brought forward. Office 365, Google and others are already using this model with phenomenal success.

If Fusion were to become local storage capable, I would think then that there would not be a cloud revenue purpose. However, Fusion has already stated that cloud storage is the only option - ever.

[Viktor94]

Thank you for the insight of the buisness model aspect !

[Anonymous]

That's the latter half of what he asked for, but the first half is a performance issue, and I think he's absolulely right. When you do a save operation, at that moment a snapshot copy should be made internally. It's this copy that should get spooled out to the cloud on a background thread of execution, allowing the user to continue working. Sometimes wi-fi, internet connections be *slow*). If more saves are done before the upload is done, it simply gets put on a queue on the background thread. By making these temp copies in memory there is, of course, no risk to the future monitizing plan.

Come to think of it, you already have automatic background saving .. it seems this could use the same code.

[charegb]

Hi @Viktor94

I'm accepting this idea with a comment and a question.

1) We already do things this way. But from your comments the performance of creating the local cache that cna be uploaded on a background thread needs to be looked at.

2) Are you blocked no creating new files or moving etc? Or is it the spinning wheel in the data panel that causes this perception when Fusion is actually responsive?

Thanks,

Bankim