2010-10-0607:51 PM - last edited on 2023-05-2506:05 PM by Rubia Torres
Our office has been utilizing the "Single File Concept" as described in the Collaboration Guide, but on our latest project this seems to be becoming overwhelming. (150,000+ sf High School, AC v.13 TW2, 2.83GB project.db) The project takes, on average, 90 min to open for one user and up to 3.5 hr's for another user. Most other activities in the project seem reasonable; Teamwork operations are quick, managing the layouts is quick most of the time, etc., although updating or reloading Libraries is also extremely slow.
I thought there may be something wrong with our LAN network, but when the file is saved as a solo project (550MB) to the desktop there was no increase in opening the file or library loading/reloading time.
Does this seem reasonable for the project/file size?, or do you think there is something other than just the size of the project leading to the speed issues we seem to be having?
We are now considering changing strategies to a "Master File Method" with separate model and documentation files. But, when I broke the files up in this manner, we seem to have problems linking to the views in the model file (constant errors, extremely slow updating, etc.) This thread ArchiCAD-Talk :: View topic - Problem with Teamwork views linked to PLN file on the forum addresses this as well. Does anyone else have experience with this method?
Another option suggested in the Collaboration Guide is to use PMK files. Seems easy enough, but when pmk files are used (Floor Plans, Sections, Elevations, Details, Schedules, etc.) you lose the ability for the Markers to Reference to the Layouts.
Anyone have suggestions or experience working with projects of this size?
