General guideline on using AWS FSx Netapp Ontap on build machine

Development Pipeline & Plugins
, ,
2

Hey Narek,

Thanks for the question here. I can’t speak to the AWS FSx Netapp Ontap configuration, as this not what we use internally. We have investigated it, and had encountered some performance challenges at scale with slow/cold starts.

I will say that our build pipeline is quite memory intensive due to it’s breadth, so I’d suggest ensuring that you have:

  1. Sufficient RAM (for code we use 8xlarge)
  2. Sufficient disk space for virtual memory + paging. As you’ve noted this may not be strictly applicable given the non-file based NFS - but I don’t have much experience or context for this.

Some things I’d try is to turn off UBA entirely in your build execution via -NoUba + MaxParallelActions-16 (I’d be interested to get your more complete build log to see exactly how many executors it’s trying locally). This should further relieve memory pressure - the wider you go the more memory you’ll consume (especially in the large PCH context).

Julian