-
|
Hi there, I wanted to know if there were some parameters that can speed up that process : As I add more files, not necessarily heavy ones, the time needed for that is increasing pretty strongly Thank you in advance for answers |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
@Seekawan There is zero tuning that can be done when fetching your online data for the first time or in a Microsoft sends all your data (files and folders) in those change sets - usually ~200-210 items at a time. Due to how the Microsoft Graph API works, these items must be fetched in order (no parallel processing). If you add The client will then process those as they come in to determine applicability based on your configuration, then finally batch them up into larger 500 bundles for final handling. The only way to speed this up this initial processing:
Once the initial processing is done, and the client has fully synced, the client will start using the /delta reference that tells the client what changes have been done online since the last full sync - this is where the dramatic speed up occurs. |
Beta Was this translation helpful? Give feedback.
-
|
@Seekawan Specifically: |
Beta Was this translation helpful? Give feedback.
@Seekawan
Each of those processing dots (
.) represent a change set bundle on Microsoft OneDrive as presented by the Microsoft Graph API.There is zero tuning that can be done when fetching your online data for the first time or in a
--resyncscenario.Microsoft sends all your data (files and folders) in those change sets - usually ~200-210 items at a time. Due to how the Microsoft Graph API works, these items must be fetched in order (no parallel processing).
If you add
--verboseyou can see this occurring.The client will then process those as they come in to determine applicability based on your configuration, then finally batch them up into larger 500 bundles for final handling.
The only…