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.
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