![]() It makes sense to decrease it especially for unstable networks. It will impact the job performance and load the Agents. Increasing this parameter will force agents to be busy with establishing and keeping connections to each other. Number of agents that can be connected to each other at a time. Increase up to 3-5 minutes for unstable networks or if there are a lot of agents and files in the job. Agent will do this less frequently and thus sped more resources on transferring files, but as as side effect current status and job performance statistics will not be updated in realtime. Increase these up to 2-5 minutes for large numbers of agents or files. update upload/download difference with each other. These three parameters define how frequently agents do the following accordingly: This parameter must comply with lazy_indexing, see here for usage examples.ĭisabling hashing at all, while "Disable differential sync" is Yes in Agent Profile does not make sense and will cause job to stuck.ĭisabling it is not advisable for Synchronization jobs, especially if agents tend to go offline periodically as other agents won't be able to download the files until file owner is back online.Ĭonnect_more_peers_interval (deprecated starting with v3.0)īe sure to add them to all agents in the job. It is similar to lazy_indexing, and applies to the file owner - the Agent which updated the file last. Some other parameters require this option to be either on or off.Ĭan be added to either Agent or Job profile. read more about using this parameter here. On the other hand, not having a file hash is a great risk in cases when files are renamed, new agents appear in the mesh, etc. It improves speed of merging folder tree and getting the job into balance (especially when only few files differ on different agents). If set to true, and pre-indexing trigger in Distribution or Consolidation job has a command to create the source path, it will be created.Įnabled lazy_indexing means that the Agent will not hash any files until some other Agent requests to download it. But it's it's disabled for sender only, the receiver will request full file, and when sender rejects this, will switch and request file pieces, which leads to excessive work traffic between agents. If it's disabled for receiving agent, the Agent will request file pieces, without significant impact on performance. If you choose to disable it, it shall be done for both - sender and receiver of files at the same time. This may reduce transfer time as fewer requests are made and fewer pieces are transferred, but if transfer is interrupted, file will be re-synced from start. Works only for non pre-seeded case. If a file is smaller than the current speed, it won't be broken into pieces. Requires restarting the Agent for changes to be applied. For agents to perform indexing in parallel as well, set parameter parallel_indexing as true as well. On the other hand, multiple parallel threads may clog the disk. If set to true, a job will have standalone drive thread and perform synchronization if parallel with other jobs. Can be increased when syncing with a cloud storage, see here for more details. ![]() May be used to find best performance on network shares. Applicable for high speed drives (fast SSD, raid). Increasing the number shall improve performance on high-latency CIFS with multiple worker threads support. Number of threads each disk uses for disk operations. As a side effect, enabling compression will cause CPU usage to compress and decompress data. NameĪdded to Agent profile in Resilio Connect v3.0.0. Each of these has side effects and may be not compatible with some other non-default parameters. ![]() Please use them with caution and only if you understand what you're doing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |