My situation: mainly multiple 2GB files, to be copied to B2 via crypt.
Multi-core x64 machine, 2GHz clock.
I see that crypt is single threaded: on a multi-core machine, it peaks out 1 core, and does not use other cores. And it seems to require to have encrypted the whole file before starting to transfer data. Result: long delays (up to 10 minutes) before start of transfer, and regular pauses in transfers when it picks up new files to transfer.
I have the impression that with the newer B2 backend these delays have gotten worse. (since I moved from 6.43.x to 6.44.2 with --b2-upload-concurrency 4)
Run the command 'rclone version' and share the full output of the command.
os/version: debian 11.8 (64 bit)
os/kernel: 6.1.0-0.deb11.11-amd64 (x86_64)
Which cloud storage system are you using? (eg Google Drive)
The command you were trying to run (eg rclone copy /tmp remote:tmp)
I see a large wait period (10 minutes+) before the upload really starts, during which the CPU is at about 115%, and a batch is completed (--transfers 10, batches of 10 complete at about the same time), the upload stalls for 1 or 2 minutes while CPU again peaks at about 115%.
Before 6.44, the initial wait was about 5 minutes, and there were no large stalls.
I can provoke a log with -vv if you want, but I have the impression you know where this is coming from.