I'm storing artifacts within Go (2.2 Enterprise) to use in subsequent pipelines.
Fetching the artifact is taking what appears to me to be far too long (It is a largish tar file of approx 600Mb), but the agent is installed on the same Red Hat server as the Go server so I'm thinking that fetch is actually just copying the file from one location on the server to another. If I do this by hand (using the cp command) it takes a few seconds, but using Fetch within Go it takes over 10 minutes.
Any thoughts as to whether I have something wrongly configured? or an explanationas to what Fetch is doing that causes the length of time to be so long.