Faster Autosave!
-
I don't get it... Why is the autosave so incredible slow?!? it's much slower than a normal save.
This is really quite annoying especially with bigger files... right now i'm working on a file that has ~100MB and every autosave takes nearly 1 min!
it's the same with small files - i have tested this with a file that normally saves in 1 second - the autosave need 10-15s!!!(sketchup v7 / win7x64)
-
So... why not disable autosave completely and manually save before every major change or 5 minutes, OR set autosave to have a considerable time gap, so that you do get some autosaved versions for the occasions when it all goes terribly wrong and splats... and you haven't done a manual save lately...
Also remember to 'Purge' unused dross, so that you aren't saving something that's twice the size it needs to be, and also occasionally run the 'Fix' tool in case there's so tangled data in the database tripping things up... -
yes... sure, i can do this - but the question for me is: Why has it to be soooo sloooow?!?
i can't see any reason why it should be noticable slower than a normal save.and compared to other 3d apps like 3dsmax the normal saving is very slow too...
-
Clearly these ARE issues that need addressing by Google... I was simply proffering a 'fix' for now...
-
thanks!
-
btw. ...the other joke is, that the autosave function only seems to be active if you are working on the model.
when i have sketchup open but work for some time in another program and come back to sketchup, after the first click in the model the autosave starts...
THIS is very annoying! Why can't this be done when i'm not working on model?!? There has been much time to do the saving before i came back!
-
Indeed the autosave function would need some tweaking... at times, my sketchup crashes and I could not figure a pattern, because making same commands later on did not crashed the program.
I have reasons to suspect that if autosaving and some resources-consuming operations are happening at the same time, it might crash SU. -
I too found autosave annoyingly slow. And I also found in V8, it is faster than it used to be, but manual save seems faster than autosave.
I brought this up a very long time ago, and also suggested a possible fix to speed it up dramatically.
UNDO has a stack of 100 operations (I counted). That has got to be a whole lot smaller than the model file.
SU should create the Autosave file from the UNDO stack, by user specified (short) time interval as is done now, and when the stack nears 100 (or XX) operations. The Autosave UNDO file just keeps building till the next manual save.
A manual save clears the Autosave UNDO file.
Then if SU abends, the recovery is to apply the Autosave UNDO file to the last saved file, but in reverse, as a "REDO".
That way almost all the work is recoverable and the autosaves should be almost unnoticeable. -
@jgb said:
I too found autosave annoyingly slow. And I also found in V8, it is faster than it used to be, but manual save seems faster than autosave.
It would be great if you guys could help to quantify this– in our lab (and in the code) 'save' and 'autosave' are expected to take the same time. With a couple caveats:
-
If you have "Automatically check models for problems" and "Automatically fix problems when they are found" enabled in "Preferences > General > Check Models for Problems" you may experience differences depending on the validity state of the model.
-
Autosave always happens when you aren't expecting it. Doesn't matter how you've set the timer, it just won't sync with your mental state while modeling.
If you feel like Autosave takes longer than Save, try timing it to see if you're right. It would be useful data for us to have.
john
. -
-
Try this plugin by TIG. I set my autosave to 30 minutes and use the archiver.rb plugin. So a search and check it out, it is fast.
Ken
-
-
@unknownuser said:
Try this plugin by TIG. I set my autosave to 30 minutes and use the archiver.rb plugin. So a search and check it out, it is fast.
Ken
This looks like a tool that is similar to SketchUp's existing "Save A Copy As...", though it automatically names the file for yu so you don't have to navigate a dialog. Are you saying that this script saves large SketchUp models faster than a simple "Save" operation?
john
. -
This may be off topic, but related. I rarely get a fix report in Validity Check. Maybe I ain't mean enough. Should Validity problems be a frequent occurrence? How frequent?
Moderator, feel free to move this. -
@jbacus said:
@unknownuser said:
Try this plugin by TIG. I set my autosave to 30 minutes and use the archiver.rb plugin. So a search and check it out, it is fast.
Ken
This looks like a tool that is similar to SketchUp's existing "Save A Copy As...", though it automatically names the file for yu so you don't have to navigate a dialog. Are you saying that this script saves large SketchUp models faster than a simple "Save" operation?
john
.I can select the archiver selection and go back to work as fast as the mouse can move to another tool. It is quick.
Ken
-
I was asked ages ago to set up a timer to remind you to archive every 10 minutes BUT it's annoying to get dialogs popping up in the middle of something and reworking it to be automatic AND wait until you've stopped some complex operation is also making it into just the bastard-child-of-AutoSave ???
-
@unknownuser said:
I can select the archiver selection and go back to work as fast as the mouse can move to another tool. It is quick.
Well, I've looked at the code, and it looks like it is doing a "model.save" to do the actual archiving operation. Which is the same code path that SketchUp executes from the File menu. Not sure why that would be faster.
TIG: Can you explain what your script is doing differently?
john
. -
I did a Save on one of my large models and it took 90 seconds. I then made a copy of the file, opened it and uses Archiver: it took 80 seconds.
I guess I don't see much advantage of Archiver over a regular Save.
-
Archiver simply uses the
model.save(name)API method to save a 'tmp' snapshot of the SKP at that second, it then copies it to an 'Archives' subfolder, renaming it with an additional date-stamp etc and erases the tmp version.
It shouldn't make any significant difference to the built-in autosave timings - it even has to copy/delete the file into the subfolder too... however, it does seem a little quicker
-
As I said earlier in this thread, "Check Validity" (if enabled in preferences) can cause a save to take longer. If a model is checked for invalid geometry, then that geometry is fixed... it doesn't have to be fixed again the next time you save a model. This might account for a small difference in save speed (~10%) between successive operations.
My guess is that optimization of the rendering pipeline has allowed you to work on increasingly large models (Bob: 80-90s save times! How large is your model?) and you're now beginning to feel a new performance bottleneck. Of course, there will always be a performance bottleneck somewhere in the system.
john
. -
@jbacus said:
My guess is that optimization of the rendering pipeline has allowed you to work on increasingly large models
Yup - I find working on 500K face models and more without much trouble. It's usually depending on transparency use and textures.
Advertisement