Tuesday, January 6, 2009

Save Locally - Save Time

Wow! Here's a pretty major and very often overlooked issue with saving files in Revit that I recently realized many people aren't aware of...

If you work in an office (or even at home with a server of some sort) you have probably always saved your Revit files the way you always did with Autocad or any other program, in the project's file folder somewhere on a local server, right?

Well Stop!

Why? Because you've probably noticed that once a project gets relatively large, say upwards of 20 Megs it gets really slow to save, it can take mutilple minutes, wasting your time, you may have even just decided that this was just one of the downsides to working with Revit's large files, it doesn't have to be!

If you save your file locally, like on your desktop even large files save fast! At the end of the day just upload the file manually to it's proper location and your fine. (Of course this is what you're doing already if you use worksets and are saving to central.)

3 comments:

cl said...

I would love to see anyone's solution to this. We have the same issue, and I've heard it from others. Using the same file, our old server saved 10 secs, the NAS we switched to saved in 1 min.+, and our new updated server saves in 45 secs. But we can save to local drive OR ANOTHER WORKSTATION on the network in around 2 secs! Our new server isn't really doing anything but handling files, and the old one was also running Exchange, but with lower save times! Same OS. The save to local / move to server isn't a good solution when the whole reason for the file server is for simplicity and safety. People forget to copy to server.

Rendersmart said...

You should never store files on a local machines as there is no redundancy. Any firm should have some form of RAID setup to ensure data is not lost throughout the day in the event of a HDD meltdown which believe me happens more often then not. Loosing 1-8hours work because you cannot wait 30secconds to save is not a workflow anyone should adobt, nor the risk of forgetting to copy over. I understand your frustration but this should not be recommended to anyone. If you workplace is slow, ask them to install a RAID 10 setup with gigtabit feeds(NOT RAID 5). Hardware is cheap these days even for small business. Eleminate risk :)

Cheers.

jimij said...

Rendersmart, well yeah, You should never just rely on a local copy of ANY file. People need to be smart and backup their data. The option we've chosen is to save locally and to use auto syncing software to perform regular local backups to the server. These occur in the background, so Revit isn't tied up at the save and you can avoid people forgetting to backup. In my experience the wait on a save to the server was sometimes as much as 5-6 minutes! Unfortunately this led most users to reduce how often they were willing to save, only saving once every couple of hours as opposed to every 5 minutes like they should! So although HDD crashes are a real issue, Revit crashing or Windows freezing is FAR more likely to happen, and it did, often resulted in 2-3 hours of lost work on a far more frequent occurrence (almost daily) rather than the once a year loss of 8 hours data from a HDD failure. Like any solution or work around, use your best judgement! Remember to back up your data!