This topic covers the configuration options available for customizing how Deploy handles large artifact deployments, including the in-memory processing threshold, executable detection regex, and JVM heap sizing guidance.
Deploy 26.1 and later supports deploying artifacts larger than 2 GB. Large artifacts are transferred using a streaming approach instead of being fully loaded into memory, which significantly reduces memory pressure during deployment. This topic covers which artifact types are supported, how permissions are handled, storage compatibility, and best practices.
This topic explains how Deploy processes archive formats internally, why the 2 GB boundary exists for ZIP archives, how adaptive permissions work when POSIX metadata is unavailable, and which storage backends support large artifacts.