Rhino freezes while saving / autosave

Rhino
1

Hi everyone , idk why but rhino get to freeze couple of seconds (like 30s for a 400mb file) , currently im working with other softwares along together , it seems like z_brush and bl_ender have found a way for the program to run while the file is being saved this will seriously improve the performance since the user don’t have to wait a long time for the file to being saved. this will reveal it’s effect when for example we need an incremental save for every 2 mins .

i tested the problem above with two hard drives , ssd and hdd together it will freeze in both .

1 Like
2

Hi Hamed -
Thanks - we have that feature request on the list as RH-55380 Wish - Background or Continuous File Saving
-wim

4

(woops ! didn’t knew crossed the redline there !) any news about saving the file while working on it ? our company is planning to move to the mac , maybe changing their modeling software , idk if mac can save the file while working on it …

5

Ok , here is a thing that im thinking about , im not any programmer , but i guess rhino is directly start to write stuff on disk after save command and freezes till save happens , but in these days softwares use some thing called BUFER which kinda saves data into the memory (ram) then writes that data back to the hard drive , i researched about options to make rhino faster while saving and i modified bellow settings
Rhino.Options.FileSettings.WriteLocalTempFileWhenSaving
and
Rhino.Options.Advanced.UseCompressionWhenSaving

which did help to reduce save time but in comparison with others thats nothing !
I tested the software under heavy load of hard drive (all of them at 100%) but rhino didn’t froze or lag or anything .
if rhino was able to save a file into some clusters ( as i remember back into the school we could call a file at certain line in basic) which every cluster refers an object and the object properties and the version of that object ( for the software to know change that object or not) , and also keep data in history as much as possible like cages and mirrors etc … the file saving wouldn’t take that long .
here is the sample that i meant ::

File name  = "Some big File"
   
  List of objects =
                            BigMesh1  , start at line 8 , size (x,y,z) , location (x,y,z) , etc ... , Latest edited ver ( 2 )
                            BigMesh2  , start at line 20635 , size (x,y,z) , location (x,y,z) , cageEdit data , etc ... , Latest edited ver (65)
                            BigMesh3 , = BigMesh2 , size (x,y,z) , location (x,y,z) , history data,// Not changed Or eddited just copied BigMesh2  and moved around 
                            And So on ...

ln 8 = Start of BigMesh1
                                           0101011001100010110100111101001 //Massive Data ...
                                           Other useless data that can be changed ...
ln 20635 = Start of BigMesh2 
                                           01010110010110000101010101110101 // another massive Data
                                           Also another useless data that can be changed aswell

and inside the rhino we’ve got the id’s of objects that has been changed since we know their versions etc ( also moving and scaling and cage editing etc are not big deal since we save them separately on top of the file )