Dividing Revit project in middle of modelling

[ofori.nelly]

I made a model with repetitive patterns and found myself with a 35MB file.
My computer has slowed down.(I have a HP with 2G RAM).

I want to divide the file into about 3 files and use worksets and linking.
I'm worried about doing it 'cos I don't know how to do it correctly.

I want some advice on how to separate the skin of the building(it's a
custom wall with some curtain wall) and maybe even divide the skin further
up since all the memory is from the repetitive pattern in the skin of the
building.

Eg. do i just make 3 copies of the file and delete the core or use
visibility settings to divide up the project.

[greg.mcdowell]

In the time you spend breaking up the model you could probably afford to buy more RAM. You did mean 35mb and not 350mb correct? 35mb is a tiny Revit file.

You can either use worksets to control what is loaded into memory or break up the model into separate files as you suggested. If it's a RAM issue I don't think it matters but if it's a speed of saving then I'd suggest the separate files approach. And yes, I think saving the file out multiple times and deleting the relevant model components is a good way to go.

[wmullett]

As greg says, this is a tiny Revit file. The problem is not the size of the file but your patterns. Hatch patterns that are used in large areas should be simple. In detail views, this can be replaced by more intense patterns.

[Scott D Davis]

There is no reason to break up a 35mb file into separate files. This is a relatively small Revit file. As suggested, look into buying more RAM, as this will be much cheaper than the time you will consume trying to split up and re-organize a model.

[ofori.nelly]

I am a student so I will be stuck with this 2Gig RAM for at least 5more months.

ps. i'm not very advanced

[ofori.nelly]

In the time you spend breaking up the model you could probably afford to buy more RAM. You did mean 35mb and not 350mb correct? 35mb is a tiny Revit file.

You can either use worksets to control what is loaded into memory or break up the model into separate files as you suggested. If it's a RAM issue I don't think it matters but if it's a speed of saving then I'd suggest the separate files approach. And yes, I think saving the file out multiple times and deleting the relevant model components is a good way to go.

i didn't see your post. thanks for the response. i'll go ahead and copy and delete. lol. lots of strong views here. architects are this aggressive? lol

[nancy.mcclure]

YES. haha. Well, not 'aggressive' per se, but of strong opinion. You're in school, so you'll see after 4-5 years of having to defend your design concepts and decisions at every go-around that if you're NOT of strong opinion, you'd be drummed out or beaten down pretty quickly! After all, it does take a certain personality to get up every day and want to show the world that, yes, you can design something better than has been done before.