![]() ![]() Unfortunately network throughput to the network share is one of the limiting factors as well as storage to be able to go faster. Binaries and system files for all supported platforms adds up to over 250gb per build and we try to get a full turnaround of these builds every 5 minutes or so. (example: \myserver\builds\myapp\version1, \myserver\builds\myapp\version2, \myserver\builds\myapp\version3)Īt EA we have a build farm that produce new builds for all supported platforms at quite a fast rate. The second reason was to improve performance when copying large amounts of data to network share where the same files are often copied over and over again but to different destinations on the same network share. The main reason EACopy was created was to be able to provide text files containing the files/directories to copy. EACopyĮACopy is an alternative to Robocopy for copying files from one location to another. SERVERADDR /C" to speed up transfers using zstd compression from the office to your home. This means that anyone can spin up an EACopyService next to the network share and then use "EACopy.exe. ![]() We have added support for having EACopyService sit on another machine than the network share to enable environments where the network share machine is not running windows (like NetApp etc). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |