When using the 64 bit version of 4D Server on macOS, the runtime of the application will use about 4 GB of memory* while usage within the app (arrays, blobs, xml, etc) can further increase this memory footprint. It is important to factor this base memory footprint in when making recommendations to your customers about RAM and Cache sizes.

*This can be observed in a brand new database by looking in the Runtime Explorer and subtracting the Used Cache from the Used Virtual Memory.

If you plan to use a cache size of 4GB with the 64 bit version of 4D Server on macOS, the runtime of 4D is also using 4GB of memory, this makes the normal usage of memory upon starting up this database would be 8GB. Running this configuration on machine with only 8GB of memory would be ineffecient because it would be guarunteed to swap memory.