Troubleshooting Performance Problems in ArchiCAD Teamwork

by GRAPHISOFT and Ed Brown · updated: 06.25.2012

This article describes common causes of slow Join, Send and Receive performance of ArchiCAD Teamwork. 

1 – Network is slow, or has high latency

Join performance depends not just on the bandwidth of the network, but also the latency. A fast network with high latency will also cause performance problems

2 – BIM server performance (RAM)

Teamwork operations involve data processing on the BIM server. In GRAPHISOFT Tech Support’s experience, inadequate amount of RAM in the BIM server is a leading cause of bad teamwork performance.

3 – Backup Scheduling

When the BIM server is performing a Backup, it may be less responsive. Make sure backups are scheduled to run in off-duty hours.

4 – Large Embedded Libraries

Even a small project can have a large database, if it has an extensive embedded library. Large embedded library is often due of imported IFC elements.

5 – Embedded Library and Hotlink from previous version files

Long join times can be due to embedded library elements in hotlinks that have not yet been migrated to the version of the host project. If the library elements reference/or are zone stamps many walls could be queried as part of a temporary migration of the hotlinks that will occur at each join. It is best to migrate all hotlinks to the current version of the host project before other teammates start joining the project.

6 – Roaming Profile is uses

If Roaming Profile is used, then cached Teamwork data is saved to a network drive, which slows down open/join times significantly. Read more about this: Change roaming profile configuration to optimize log on time for teamwork users

  • Was this Helpful ?
  • 0   ​2

Subtopics

Layer Combination Oddities

Issue In a teamworked project some layer combinations settings are only visible to one teamwork user. Send and Receive does not resolve the discrepancy. Cause A new layer is added and layer combinations are adjusted without reserving the Teamwork layer…

Slow Send and Receive

Issue Send and Receive takes a long time Cause Most common first, least common last: Not enough memory for the size of the project Fragmented Hard Drive and/or available space is less than 15% of the drive's total space Bandwidth of network low Anomolies…

Roaming Profile Configuration

Issue When you are using a Roaming Profile on Windows for Teamwork, log in and log off becomes very slow and the size of the User Profiles increase to several Gigabytes. Cause The default location for many of the ArchiCAD home folders, especially TWData…

Project Locked Has Hotlinks

Issue Several users of the same Teamwork project find their project hanging/frozen. Cause A deadlock has occurred with a hotlink update Solution It is highly suggested that with sites implementing teamwork, they limit authority of hotlink updates and…

Related content

Roaming Profile Configuration

Issue When you are using a Roaming Profile on Windows for Teamwork, log in and log off becomes very slow and the size of the User Profiles increase to several Gigabytes. Cause The default location for many of the ArchiCAD home folders, especially TWData…