ArchiCAD vs. Revit: what hardware do you actually need

Studios considering the purchase of new workstations often ask for a universal "best CAD configuration". However, the answer depends on whether the team works in ArchiCAD or Revit: both programs have different architectures and stress hardware differently. This article compares the actual requirements of both tools and shows where investment pays off and where it is unnecessary.

Different architecture, different requirements

Revit is built on a parametric model where most key operations, navigation, synchronization, editing, run predominantly on a single processor thread. We have discussed this in detail in the article. on workstation optimisation for RevitIn contrast, ArchiCAD handles more operations in parallel, especially during rendering and certain types of model recalculation, and therefore makes better use of processors with a higher core count.

The difference is also evident in the team's collaboration method. Revit typically works with a central model via Revit Server or BIM Collaborate, while ArchiCAD uses its own Teamwork server. Both approaches have similar network requirements but differ in management and licensing details.

Comparison of hardware requirements

Differences in hardware requirements also relate to how both applications handle memory when working with large projects. Revit keeps a large portion of the model in memory at once, making it more sensitive to insufficient RAM for extensive buildings with many linked files. ArchiCAD, on the other hand, can work with the model in parts, which partially compensates for lower memory capacity in medium-sized projects. In practice, this does not mean you can save on memory; it simply means the threshold at which insufficient RAM starts to cause issues is somewhat higher.

Where savings are possible

• Top-tier GPU model series - if the studio does not render in V-Ray or Enscape, a mid-range card is sufficient for both programs.
• Extremely high number of CPU cores in Revit - For pure Revit work, 16 or more cores are not utilised; funds are better invested in higher frequency.
• The most expensive NVMe drives with extreme write speeds - for smaller studios with projects up to tens of gigabytes, a mid-speed NVMe generation is sufficient

Where cutting corners is not worth it

• RAM - for both programs, insufficient memory is the most common cause of slowdowns and freezing; 32 GB is today's realistic minimum for production work.
• NVMe disk for project data - The difference between SATA and NVMe is noticeable with both tools when synchronising large models.
• Quality network infrastructure - A slow or unstable network can hinder team collaboration more than any component in the workstation itself.
• Cooling - An overheating processor reduces performance (throttling) in both applications equally; a cheap case with insufficient airflow is a false economy.

Recommendations based on studio size

A small studio of up to five people can get by with one well-configured workstation per architect: a higher CPU frequency, 32 GB RAM and an NVMe disk will cover most work in both programs. A medium-sized studio with ten or more workstations and shared central models should also invest in network infrastructure and high-performance storage, there the bottleneck often shifts from the workstation itself to the NAS or server, as described in the article on choosing a NAS for an architectural studio.

Whether the studio works in Revit, ArchiCAD, or both, it pays to consult before purchasing hardware: a poorly chosen configuration costs more in lost time than the difference in purchase price.