Enable/Disable the autosave function

Follow

Alex Cross

• October 06, 2017 09:36

I'm very glad there's autosave, but right now it appears to be autosaving after every single thing I do, and it takes longer to save than it does to make each change. Currently have a code I copied from another node, with 6 different "tasks" in it, and on each one I'm updating a field name by copy and pasting, and after every paste it autosaves, so a job which should take me 10 seconds to do ends up taking a minute or so.

Is there any way to change the autosave function to be every 5 minuntes, or every 20 actions, rather than every time I click the mouse? (Unless this is some weird bug..?)

Thanks,

Alex

0

• 

  Adrian Williams

  • October 13, 2017 10:39

  Hi Alex,

  Dataverse is not auto-saving as such. The Dataverse application is a multi-tier web application. The web application is essentially stateless - changes to a data flow and node configuration updates are secured in the Dataverse database component. Your browser is rendering the Dataverse web app and whenever a change is made the app uses REST API requests to update the 'back-end'. It is probably the round-trip latency for these requests and database updates that you are seeing. Work has been done to optimize the performance of these actions, e.g. by batching up multiple updates where appropriate, but there is almost always room for improvement. The available RAM and the speed of the machine's disk has a big impact on the overall performance, and a SSD provides improved responsiveness compared with using a traditional HDD. Would you be able to provide details of your machine - i.e. CPU, amount of RAM and disk type?

  Many thanks,

  Adrian

  0

  Comment actions Permalink
• 

  Alex Cross

  • October 13, 2017 11:56

  Hi Adrian,

  Thanks for your response. I'm currently running 8GB RAM with an i7-4600 @ 2.1GHz, with an SSD.

  Just to clarify, the symbol which made me think "auto-save" is the rotating white arrows which appear where the green progress cirlce appears when running nodes. This often happens every every 2nd or 3rd click, and depending on the number of nodes in use, can take upwards of 10 seconds each time.

  Thanks,

  Alex

  0

  Comment actions Permalink
• 

  Adrian Williams

  • October 13, 2017 15:36

  Hi Alex,

  would you be able to provide an indication of the number of nodes within the data flow?

  Does the latency occur with specific data flows or does it occur if you create a new data flow and paste the code into a single node on the canvas?

   

  Thanks,

  Adrian

  0

  Comment actions Permalink

Please sign in to leave a comment.