The Global ARCHICAD Community

Stay informed. Get help. Share your knowledge.

Discussions about managing ARCHICAD in architectural practices (Project Setup, Templates, Attributes, Migration, Compatibility with Previous Versions, Preferences/Work Environment, User/Project/Application Administration/Management etc.)

Moderators: Karl Ottenstein, LaszloNagy, ejrolon, Barry Kelly, gkmethy

#300701
HI,
This might have been asked in the past but from your collective experiences:
What is the most optimum file size for a Teamwork file before performance becomes an issue?
Same question for a Solo file.

And what are the factors that most affect performance once that "magic number" is breeched?
#300717
Hi,

If you are looking for an optimized file, then file size is not the right direction. Even a 100 MB file can be awfully slow while a 3 GB project goes very well on the same computer.

Instead, I suggest to keep your attributes clean, do not use too many Solid Element Operations (SEOs), limit the number of polygons, etc.

When a project is well structured and organized, and even the computer under it matches the needed resources, it should be right.

Kind regards,
#300726
nbalogh wrote:
Thu Aug 15, 2019 12:01 pm
..., limit the number of polygons, etc.
And, to find out if your project is heavy with polygons...and if so, which objects are responsible (and should be deleted or simplified), get the PolyCount add-on which is part of the Goodies package:
https://www.graphisoft.com/downloads/goodies/
#300731
Slow files are more a symptom of over-modelling or staff not understanding the importance of line-work. Also, being aware of how your model is generated on screen, on layouts and by printers.
When you are modelling you are actually covering many lines and fills with other lines and fills to achieve a particular graphic. Reduce detail where possible.
Don't forget that every line means something. Don't overcomplicate your line work.
Look where are your lines coming from. Are they lines, or fills, objects or mods. Are they transparent or solid and how does your hardware deal with the software. Eg a vector fill will be more efficient than a symbol fill for floorboards.
Really, GS have let us down by not letting us build better vector fills, and forcing the defaults to symbol fills. Try swapping symbol fills for vector fills and unleash the speed. Even in wall composites. Use symbol fills for detailing only.
Don't forget to set your workspace to your hardware capabilities.
Finally, how big are your loaded libraries and attributes? Chances are they too are killing your speed too.
Meh, it's a big topic. Probably too big for here. Hope this gives you some ideas though.
#300732
Thanks for the contributions.
We currently have a large Teamwork project (6Gb) that is glacial at the moment and there is discussion about throwing more RAM at the problem. I disagree and was seeking some corroboration for my position on the matter.
#300738
Check the Embedded Library - if it has many objects, it makes working horrible in Teamwork. Empty its content and instead use objects as BIMcloud Libraries. This can be a huge improvement on performance.