You were right, there were one difference between deployment of v14 and v15. It was NAS itself, witch for V15 is brad new and super-fast connected with 1Gb line. As it appears, rsync by its nature tries to “eat as much it can” and for large files it boils I/O, hence CPU. And for VM it is even more dangerous, like in my case.
Solution is provided by rsync itself: use command - --bwlimit=KBPS (limit I/O bandwidth; KBytes per second).
This option allows you to specify a maximum transfer rate in kilobytes per second. This option is most effective when using rsync with large files (several megabytes and up). Due to the nature of rsync transfers, blocks of data are sent, then if rsync determines the transfer was too fast, it will wait before sending the next data block. The result is an average transfer rate equaling the specified limit. A value of zero specifies no limit.
You were right, there were
You were right, there were one difference between deployment of v14 and v15. It was NAS itself, witch for V15 is brad new and super-fast connected with 1Gb line. As it appears, rsync by its nature tries to “eat as much it can” and for large files it boils I/O, hence CPU. And for VM it is even more dangerous, like in my case.
Solution is provided by rsync itself: use command - --bwlimit=KBPS (limit I/O bandwidth; KBytes per second).
This option allows you to specify a maximum transfer rate in kilobytes per second. This option is most effective when using rsync with large files (several megabytes and up). Due to the nature of rsync transfers, blocks of data are sent, then if rsync determines the transfer was too fast, it will wait before sending the next data block. The result is an average transfer rate equaling the specified limit. A value of zero specifies no limit.