material take off schedule and speed

[Justin Marchiel]

I have a material schedule created on a fairly small job (just starting out). I am wondering if have the schedule created so early in the job will slow it down. My thought being that it has to constantly update the schedule everytime something is create/deleted/strectched, etc (i noticed some small time glitches with the schedule in place, ie things not responding as quick as i would expect).

Does anyone have any experience with scheduling everything? Does it speed up if the schedule view is closed? Should the schedule be added later in the process? Logically i would think that it should not affect the speed since the whole project is essentially a large database anyways. the project database is updated, so it should not adversly affect the speed if i have a schedule.

I tend to ramble so i hope the above makes sense.

Thanks

Justin

[dbaldacchino]

I wouldn't add schedules to the project just because you can, but I'd add what is necessary when is necessary. For instance if you don't need room volume calvulations, then uncheck that option. If you don't need wall schedules, then don't create one, or delete it after experimenting. I don't think schedules should adversely affect performance, but they're being computed after all (it's just another view). But don't hold your breath until the end of the project. Build the views (and schedules) as you progress and deem fit.

[Wes Macaulay]

It seems to me that in one of the releases of Revit in the last 18 mos that scheduling was demand loading in some way to improve performance. I have never heard that schedules hurt performance any more than adding a section does. Because when you think about it, a schedule is no more a view of the database than a section is.

[Dimitri Harvalias]

I agree Wes. David does make a good point about room volumes though. If you don't need them calculated dynamically then turn them off in the room object. Revit needs to consider the volumes of rooms every time something gets moved and that can slow things down considerably.

[Justin Marchiel]

That is kind of what i was thinking, but my original thinking (as noted by wes) is that REVIT does all these function internally anyways and you are just creating a view to report them.

Thanks for the replies. I try not to make uneccessary view, and delete unused ones, but there are some "working view" that i create that are really helpful to keep and go back to.

THanks

Justin