Connect Management Console
OS
- Windows 7 or later (64-bit only)
- Windows Server 2008 R2 or later (64-bit only)
- Windows Server 2012 R2 or later (64-bit only)
- Linux x64 (kernel 2.6.32 and newer, glibc 2.17 and newer)
- Ubuntu 16.04 and newer
- CentOS 7 and newer
WebUI
- Most Internet Browsers
- For Internet Explorer, version 11
Hardware requirements
| Tier | CPU | RAM |
| 50 Agents 10 jobs each |
Intel Core i5 or similar, 4 cores |
6 GB |
| 100 Agents 50 jobs each |
Intel Core i5 or similar, 4 cores |
8GB |
| 1,000 Agents 300 sync jobs each |
Intel Core i7 or similar, 8 cores |
10GB |
|
10,000 Agents |
Intel Core i7 or similar, 16 cores |
32GB |
Storage space requirements
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.
All measurements are approximate for average load on the MC.
Job runs database requirement: around 4MB per every 100 job runs.
Each backup archive takes as much space as job runs database multiplied by number of backups (see here for more details about backups).
MC logs rotate as the log file reaches 100 Mb, the log is zipped. No more than 10 log files are kept (can be changed in MC configuration file).
Below are the measurements for storage space taken by events.
(These are clean tests when MC is only busy with writing events - no reading events, no other heavy processes, etc. Also, events filters are not applied. Real life results may vary.
When measuring system load, in tiers marked as 1->n or n->1, MC agent is used as this “1” agent. Hardware: Intel® Core™ i7-3770 CPU @ 3.40GHz 28 GB DDR3 RAM)
|
TIER |
STORAGE |
System Load on MC* |
|
|
All events |
File events |
CPU / RAM |
|
|
2 agents, 1 sync job, 100 files, updated several times per hour |
40 Mb per day |
31.7 MB |
3.2% / 200 MB |
|
10 agents, 1 sync job, 100 file updates per minute |
30 Mb per hour |
412 MB |
1.9% / 360 MB |
|
50 agents, 10 sync job, 1000 files each, updated several times per hour |
400 Mb per day |
5.9 GB |
30.27% / 900 MB |
|
200 agents, 5 sync job each, 1000 files each job, updated several times per hour |
50 GB |
38% / 1.2 GB |
|
|
10 agents, transfer 1 to 9, 100 files and a post_download script, started hourly |
60 Mb daily |
41.3 MB |
1.9% / 76 MB |
|
100 agents, transfer 1 to 99, 100 files and a post_download script, started hourly |
600 Mb daily |
395 MB |
2.1% / 140 MB |
|
100 agents, transfer 99 to 1, 2000 files and pre-indexing script, 12 runs per day |
statistically insignificant |
2.2 GB |
16.5% / 1260 MB |
|
1000 agents, transfer 999 to 1, 2000 files and pre-indexing script, 12 runs per day |
statistically insignificant |
9.8 GB |
47 % / 2.02 GB |
|
20 million files, 1 sync job. 5 agents all RW with peer-2-peer enabled. 1000 files is updated hourly. |
statistically insignificant |
12 GB |
6.5% / 1680 MB |
|
10 million files, 1 sync job. 3 agents all RW with peer-2-peer enabled. 1000 files is updated hourly. + enabled NTFS permissions by group |
statistically insignificant |
10 GB |
7.21% / 1800 MB |
|
20 million files, 1 disrt job, 1 to 1 transfer. Transfer in batch by 100k files |
statistically insignificant |
500 MB |
9.3% / 1750 MB |
Connect Agents
OS
- Mac OS X 10.12 Mavericks or later, M1 chip is supported starting from version 2.12 (For Transparent Selective Sync TSS - Mac OS M1 Big Sur 11.3.1. TSS is not supported for Mac OS 12)
- Windows 7 or later (32/64-bit); if Agent UI used - IE9 or newer
- Windows Server 2008 R2 or later; if Agent UI used - IE9 or newer
- Linux i386 (glibc 2.17*)
- Linux x64 (glibc 2.17 and newer)
- Linux ARM (glibc 2.17 and newer)
- Linux ARMHF (glibc 2.17 and newer)
- FreeBSD 11 and newer
- Android 4.2 and newer
- NAS (Please contact your sales representative for NAS device support)
Also available for: Linux build for glibc 2.4 for ARM, ARMHF; Linux build glibc 2.3 for x86, x64 (Please contact support for these builds)
Minimum hardware requirements
Based on number of files
| Tier | CPU | RAM* |
| < 100,000 files | single core, ARM, x86 or higher | 512 MB |
| < 1,000,000 files | 2 core, ARM, x86 or higher | 2 GB |
| > 1,000,000 files | 4 core, ARM, x86 or higher | 4 GB minimum. 2 KB per file with an option to limit memory usage by time window based file monitor |
Based on expected speed of transfer
For expected speed of 5Gbps, this is recommended hardware:
| CPU | Xeon E5 2600 v4 series or i7-7000 series, with 4 cores or more. Minimal frequency 2GHz. |
| Memory | 16GB or more (adds to files' based requirements above) Minimal memory bandwidth throughput of 10GBps is required. |
| NIC | For extension cards, extension slot must support full 4 lines for PCIe 2.0. Link aggregation shall be avoided. For NUMA machines with some CPU slots empty, network card PCIe slot should connect to occupied CPU slot. |
| OS | For Windows OS, only Windows Server can provide such expected speed, Windows server 2019. Other platforms shall meet hardware requirements above. |
Based on expected speed of cloud storage
| EC2 agent, <1 Gbit | t3.xlarge instance and below |
| EC2 agent, >1 Gbit | m5d.12xlarge instance and greater |
| Azure agent, <1 Gbit | D4s v3 instance and below |
| Azure agent, >1 Gbit | D14 v2 instance and greater |
| Google cloud, >2 Gbit | n1- standard-64 and greater |
*Agent memory consumption
Connect Agents consume approximately 2 KB of RAM per file (example: for 4.5 Million files Connect can consume up to 9 GB of RAM). Using time window based file monitor, you can limit memory usage.
Memory consumption
Memory consumption may double when syncing either NTFS or Posix permissions depending on the number ACLs applied per file.Storage space requirements
Total storage space required is the sum of space taken by jobs database files, backups created after update, logs (some static value as they rotate) and events.
All measurements are approximate for average load on the MC.
Jobs database requirement: around 2Kb per file and each subfolder (or 4 KB of file permissions are synced), in each of Synchronization job. For example, two sync jobs, one has 1mln and the other - 3 mln files, will take up to 8 Gb of storage , or up to 16 Gb if file permissions are synced.
On each update, the Agent creates backup folder with database files.
Debug logs rotate as the log file reaches 1Gb, the log is zipped. No more than 100 log files are kept.
OS
- Windows 10 or later (64-bit);
- Windows Server 2008 R2 or later;
- Linux x64 (glibc 2.17 and newer)
Minimum hardware requirements
Based on number of files
| Tier | CPU | RAM* |
| < 100,000 files | single core, ARM, x86 or higher | 512 MB |
| < 1,000,000 files | 2 core, ARM, x86 or higher | 2 GB |
| > 1,000,000 files | 4 core, ARM, x86 or higher | 4 GB minimum. 2 KB per file with an option to limit memory usage by time window based file monitor |
Based on expected speed of transfer
Note: with indirect connection through a proxy speed deterioration of up to 10% may be observed compared to direct tunnel between Agents.
For expected speed of 5Gbps, this is recommended hardware:
| CPU | Xeon E5 2600 v4 series or i7-7000 series, with 4 cores or more. Minimal frequency 2GHz. |
| Memory | 16GB or more (adds to files' based requirements above). Minimal memory bandwidth throughput of 10GBps is required. |
| NIC | For extension cards, extension slot must support full 4 lines for PCIe 2.0. Link aggregation shall be avoided. For NUMA machines with some CPU slots empty, network card PCIe slot should connect to occupied CPU slot. |
| OS | For Windows OS, only Windows Server can provide such expected speed, Windows server 2019. Other platforms shall meet hardware requirements above. |
*Proxy memory consumption
Resilio Proxy consumes around 2 KB of RAM per file (for example: for 4 million files Proxy can consume up to 8 GB of RAM).