12/17/2023 0 Comments Resilio sync nasStandard_F32s_v2 for speed up to 9 Gbps (same region to sync files between storages) Read/write speed more than 1.2 GB/s for speed of 10 Gbpsīased on expected speed of cloud storage EC2 agent, 1 Gbit Other platforms shall meet hardware requirements above. Minimal frequency 2GHz.ġ6 GB or more (adds to files' based requirements above) Minimal memory bandwidth throughput of 10 GBps is required.įor extension cards, extension slot must support full 4 lines for PCIe 2.0.įor NUMA machines with some CPU slots empty, network card PCIe slot should connect to occupied CPU slot.įor Windows OS, only Windows Server can provide such expected speed, Windows server 2019. Xeon E5 2600 v4 series or i7-7000 series, with 4 physical cores or more (double that on a VM). More than 8000 containers are supported but hardware requirements will need to be determined based on size and use case.įor expected speed of up to 10 Gbit, this is recommended hardware: CPU ~300 MB/s as shown in the diagnostics section of the console.ĥ00-700 MB/s as shown in the diagnostics section of the console. Profile Container Use Case Deployment Size 2 KB per file with an option to limit memory usage by time window based file monitor NAS (Please contact your sales representative for NAS device support)Īlso available for: Linux build for glibc 2.4 for ARM, ARMHF Linux build glibc 2.3 for x86, 圆4 (Please contact support for these builds) Minimum hardware requirements.Agent UI - IE11 or newer (pre-3.0.0 Agent support IE9 and newer) Mac OS 13 Ventura is supported starting from Resilio Connect version 3.4.1 M1 chip is supported starting from Resilio Connect version 2.12 + enabled NTFS permissions by groupĢ0 million files, 1 dist job, 1 to 1 transfer. 3 agents all RW with peer-2-peer enabled. 1000 files is updated hourly.ġ0 million files, 1 sync job. 5 agents all RW with peer-2-peer enabled. Hardware: Intel® Core™ i7-3770 CPU 3.40GHz 28 GB DDR3 RAM)Ģ agents, 1 sync job, 100 files, updated several times per hourġ0 agents, 1 sync job, 100 file updates per minuteĥ0 agents, 10 sync job, 1000 files each, updated several times per hourĢ00 agents, 5 sync job each, 1000 files each job, updated several times per hourġ0 agents, transfer 1 to 9, 100 files and a post_download script, started hourlyġ00 agents, transfer 1 to 99, 100 files and a post_download script, started hourlyġ00 agents, transfer 99 to 1, 2000 files and pre-indexing script, 12 runs per dayġ000 agents, transfer 999 to 1, 2000 files and pre-indexing script, 12 runs per dayĢ0 million files, 1 sync job. When measuring system load, in tiers marked as 1->n or n->1, MC agent is used as this “1” agent. (These are clean tests when MC is only busy with writing events - no reading events, no other heavy processes, etc. No more than 10 log files are kept (can be changed in MC configuration file).īelow are the measurements for storage space taken by events. MC logs rotate as the log file reaches 100 Mb, the log is zipped. Job runs database requirement: around 4MB per every 100 job runs.Įach backup archive takes as much space as job runs database multiplied by the number of backups (see here for more details about backups). Total storage space required is the sum of space taken by job run database files, MC backups, logs (some static value as they rotate) and events.Īll measurements are approximate for average load on the MC. Management console version 3.4.X+ requires CentOS or newer.Read this article for instructions on checking library versions. Windows Server 2012 R2 and newer (pre-3.0.0 versions support Windows Server 2008 R2 and newer) 8.1 and newer (pre-3.0.0 support Windows 7 and newer)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |