topic Re: Low Archicad Performance (Teamwork/Local) on High-End Hardware in General discussions

Low Archicad Performance (Teamwork/Local) on High-End Hardware

ionico — Mon, 09 Feb 2026 14:38:00 GMT

Hi everyone,

We are facing an intermittent but critical issue in our office: extremely long loading times when opening certain Archicad files, along with very slow Teamwork operations (reserving, sending/receiving). The problem primarily affects Teamwork projects, but sometimes it also impacts heavy local files (.pln). We are trying to find the bottleneck, as we have already ruled out hardware and network issues.

Workstation Specs:

CPU: AMD Ryzen 9 7950X
RAM: 128 GB DDR5
Archicad Version: 27 (Build 5003)
BIMcloud Basic Version: 2023.3 (28.0.46.4603)

Infrastructure:

Network: Local LAN, stable 1 Gbps (verified true speed).
BIMcloud Server: Hosted locally, on the same subnet as the workstations.

The Issue and Observations:

Opening certain Teamwork projects can take up to 30–40 minutes.
Teamwork operations (Reserve, Send & Receive, Release) take an abnormally long time.
Opening certain local files can also take up to 30 minutes.
During this "hang" while loading, resource monitoring shows almost no system load.
CPU utilization hovers around 20–40% (no spikes).
RAM is far from being maxed out (plenty of free memory available).
Network activity is practically non-existent (minimal traffic).

It feels like Archicad is waiting for something, or there is a timeout occurring when accessing libraries or external hotlinks, but we can't seem to track down the exact cause.

Troubleshooting Steps Already Taken on "Problematic" Projects:

Cleaned up embedded libraries, attributes, layouts, drawing views, layers, etc.
Re-uploaded the "clean" project to the BIMcloud server.
Eliminated complex high-polygon geometry. We use only standard libraries and tools, with no third-party add-ons.
Checked the allocated disk space on the BIMcloud server (we have about 200 GB of free space left).

This issue specifically affects large-scale projects that contain a lot of geometry and external hotlinks to other .mod files and external Teamwork projects. Empty or lightweight files work incredibly fast. We design objectively massive projects, but we already heavily optimize the geometry, the project structure, and the hotlinks. We have reached a point where there is literally nothing left to simplify or purge, which is why I am asking for help.

Has anyone encountered similar behavior on modern high-end hardware or with these specific versions of Archicad? I would highly appreciate any hints or pointers on where to dig next. Thanks in advance!

Re: Low Archicad Performance (Teamwork/Local) on High-End Hardware

Laszlo Nagy — Tue, 10 Feb 2026 00:50:28 GMT

Can you give a few pieces of info about the problematic project?

1. What is the size of the project file if you save a PLN to your local drive?

2. How many Layouts do you have in the Layout Book?

3. What is the polygon count in 3D?

4. Do you have large image files or DWG/DXF files placed in the Project using the Drawing tool?

5. Do you have Point Clouds loaded in your projects? How large are they?

6. Have you performed many SEOs in the project?

7. Do you have Trace Reference saved in Views or Views used as Trace References in various Viewpoints?

7. There was one suggestion by someone recently: Do you have the "Fade Environment" checkbox checked in the Desing Options Palette? Do turning it off make any difference?

8. There was also another thing suggested recently:

Everyone leave the TW project
Start a new empty Project in Archicad
Delete everything from the Local TW Data folder
Close Archicad
Restart Archicad and
Rejoin the TW project with Local Data now gone.

Re: Low Archicad Performance (Teamwork/Local) on High-End Hardware

ionico — Tue, 10 Feb 2026 09:44:14 GMT

After saving the problematic project as a local .pln file, its size is 1.05 GB (whereas on the Teamwork server it occupies 2.5 GB).
The Layout Book contains a total of 75 Layouts.
Polygon count (calculated using the Polygon Counting Tool): 1,702,103. Notably, the Curtain Wall tool accounts for 40% of the geometry.
No, there are no placed DWG drawings in the project.
There are no Point Clouds.
No, I am not using Solid Element Operations (SEO).
No, we do not have views saved with Trace & Reference enabled. There are also no such views placed on the Layouts. We use the Trace & Reference function during work, but usually turn it off immediately after use.
Yes, we use Design Options, and we usually disable the "Fade Environment" checkbox. We do not observe any performance difference between having "Fade Environment" on or off.
We have already tried a similar scenario. We saved the Teamwork project locally, then shared it to the BIMcloud server as a duplicate of the "problematic" one, after clearing the local Teamwork data. Unfortunately, this did not help.

Re: Low Archicad Performance (Teamwork/Local) on High-End Hardware

Laszlo Nagy — Tue, 10 Feb 2026 14:21:47 GMT

It may be advisable for you guys to contact your local resellers. They are probably more experienced in what else could be causing this and will be able to help you in pinpointing the exact source.

Re: Low Archicad Performance (Teamwork/Local) on High-End Hardware

Mahmoud Qenawi — Wed, 11 Feb 2026 09:30:40 GMT

Hi all,

Based on the given data mentioned above & asking Google AI, here’re some reasons you should check I hope it helps.

Re: Low Archicad Performance (Teamwork/Local) on High-End Hardware

Turit — Wed, 11 Feb 2026 14:27:57 GMT

Is there a fence modeled with a railing tool?
In my experience, a long railing results in a very large performance drop.

Re: Low Archicad Performance (Teamwork/Local) on High-End Hardware

karsten_bauschert — Wed, 11 Feb 2026 16:10:36 GMT

We are sometimes facing performance problems with our bigger projects as well,
so the measures already taken or suggested sound very solid to me with not much to add.

Sometimes we find major culprits (network, messy libraries, solid element operations, IFC hotlinks or layouts..) but some projects just remain slow.
Escalating the issue to a Graphisoft support is the way to go.
This might even rise the demand at GS for better troubleshooting features to be developed and implemented.

Also slightly off topic, but the high polygon count from the curtain wall tool is most likely a result of round profiles,

similiar as modeling with the railing tool and using round (and even hollow = x2) poles or lattice.

This creates many many polgons as Archicad cannot create real bend surfaces.