Showing posts with label Performance. Show all posts
Showing posts with label Performance. Show all posts

Sunday, April 20, 2014

Revit 2015 Improved Performance

The Revit Clinic's recent post describes how Revit 2015's performance compares with Revit 2014. Here's the graph they provided to compare the results for various operations in both versions.


I find it a bit surprising that Autodesk has not made a bigger deal of this, especially considering the general malaise felt by users to the quantity and specificity of new features. I suppose improving performance isn't a sexy thing to talk about but it seems to matter in racing? Why not with software? It improves the user experience. It's amazing how loooong 1-2 seconds can feel.

Regardless of the number of features I'll always appreciate improved performance...bring it on.

Tuesday, December 11, 2012

Applying Visibilty Graphics Overrides

This might be obvious but you can apply changes to views much faster if you don't have any views open that show model elements. Now that it is possible to alter the properties of a view without actually opening it, because the Properties Palette will display a selected view's propeties when you select it in the Project Browser, this means we can edit its visibilty graphics settings even if it isn't open.

It is particulary evident when a project has many linked files. You can alter a view for the first floor but if another floor's view is open Revit seems to spend time thinking about that one too, even mention the linked files.

If you are in the habit of using a synchronize with central view or bulletin board drafting or legend view then open that view and close all others before you dive into overriding view graphics or applying view templates.

Sunday, December 09, 2012

Views on Sheets

When you have to add views to sheets just the task itself can take a long time. You will find that trying to put a view on a sheet will take less time if there is nothing visible in the view. Try it. Close all the worksets and place a view on a sheet. Now do the same thing with all the worksets Open. Even a modest size project should see a difference. It isn't that surprising. Why don't more people think of it then?

If you are using guide grids to position views consistently you'll need to be able to see at least some grids or reference planes but not much else. Next time you find yourself waiting for views to generate as you place them on sheets remember to close worksets or at least reduce how much Revit needs to show while it is doing it.

Friday, March 23, 2012

Improve Your Borrowing Experience

When you select an element and move it Revit has to see if it is currently borrowed by anyone else. This is referred to as transparent element borrowing. Click on a wall and drag it to another location. The slight or pronounced delay you "feel" or "see" between starting to drag and seeing it happen is affected by the "back office" work that Revit does between your local file and the central file.

You can alter the perception of responsiveness some by borrowing elements explicitly instead. I wrote perception because it may not actually take less time overall but you will experience less lag/drag/delay if the borrowing process is already sorted out.

What I'm suggesting is that you select the elements you intend to work on first, then right-click and choose "Make Elements Editable". This is an explicit instruction to Revit, "I want to borrow these!". It will check and let you become a borrower of everything that is current available. Anything that isn't will generate a message to that effect. You'll still have the rest though.

This means you open a view and decide where you want to work, select elements and make them editable. Then go about your business. Synchronize with Central when you finish with them...repeat.

Remember that the right-click option "Make Workset Editable" is becoming an Owner of a "shelf" and that normally isn't the best strategy. It will however accomplish the same thing as I suggest above, just for potentially many more elements than you need. Read the post from the other day regarding the notion of "Editable".

Tuesday, February 21, 2012

The Big R is Puzzling me with Poor Performance

I've got a recurring issue, since about December that is. I did some extended work for a client and we set things up so I could have access to resources without actually joining their domain (adding my PC to their network formally). I've done this for years but I haven't experienced this however.

When I click on the Big R (application button), to start a new project or open something, I have to wait as long as 60 seconds sometimes before it expands to display the menu. I've been primarily using Revit MEP but occasionally Revit Architecture too. They both exhibit the same sluggishness response to using the Big R. Revit Structure 2012 doesn't seem to be suffering from this however. Also if I just click the Open icon on the Quick Access Bar there is no delay. None of the Revit 2011 versions seem to be bothered by it either but I didn't use them during the last couple months either.

Some additional clues are:
Was connected to shared resources (drives and printers) without being added to the domain
Was using a Named Network Location (not a mapped network drive)
Have since deleted journal file data
Have since removed all Places referencing these shares
Have removed the shared printers
Removed references to invalid locations in Revit.ini files (main and user)
Removed CMDKEY stored information related to past external resources
Have done registry cleaning for references to the past network locations
Have removed the most recent installed external applications
Have a certain version of Revit installed that isn't supposed to be installed side-by-side

With all that in mind, when I revisited my .ini files tonight I removed all references to recent files and the performance is back to normal for now.

Any readers also experiencing similar sluggishness? Resolved it? Lemmeno