First sync in progress, weird numbers for remote items created, deleted... is it normal?

[nonobio]

@laurent

In your case I would guess that it won't make a difference because the slow down is not due to the net connections but (probably) due to writing data to disk.

Ok, that's what I thought I understood. But even if it's not the fastest, It's still an SSD. Unless he has a problem... I'm going to do disc bench tests to see if I have a problem with my SSD.

@laurent

Normally once you are done with the initial sync, it should be fine, there would be 2 or 3 items to be synced now and then and that's it.

That's what I thought too. But I don't touch anything and every 5 minutes there are hundreds of objects created . I checked, OCR is disabled in the options.

@laurent

So I don't know why it's still synchronising in your case - maybe the initial sync is not really completed, or something is modifying your data?

Is it possible that it's just that?
Joplin repeatedly saying it's over when it's not? (Joplin making jokes? )

I imagine that the size of the data should be equivalent between my Joplin folder on my PC and the one on my NAS (the synchronization target), but there is a big difference which could lead one to believe that there is only the half sync completed:

@laurent

Do you see any repeating messages, even when you're not doing anything, in the console? (Under Help => Open dev tools)

I just looked after restarting Joplin in safe mode: I have a lot of "DevTools filed to load source map..." that you told me I could ignore, and otherwise I have lines like these:

13:19:30: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local 393bd89016e060feaa48f3438abebd1e)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:19:33: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local 31312e2627567a000205808786002cda)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:19:35: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local 21fd64816c88b6cf46480091dcfb2594)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:19:36: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local f50e2c4dfee6e0101b39369cd8d1fc13)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:19:41: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local 9c9e8a9daa306d630bc55ae90e5068b3)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:19:48: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local 8ba94681d3f15905fe60d1ee91094375)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:19:51: RevisionService: maintenance: Starting...
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:19:51: RevisionService: maintenance: Service is enabled
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:19:51: RevisionService: collectRevisions: Created revisions for 0 notes
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:19:51: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local 8410c564fc2a41b51274e85e15e06f8a)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:19:53: RevisionService: maintenance: Done in 2097ms
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:19:53: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local 75c940dfab96b2f5d06017512f545595)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:19:55: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local 6b8ca920a8857f9b0c1bc566d490e61f)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:19:57: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local 608c492b5b06ac0c07f8997cdf910ad8)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:19:59: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local 56d2685479186df6ef118c1a51f267c9)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:20:01: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local 507b766699c672d87436ac55db70e548)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 13:20:03: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local 307d1fa520228cb0385a59f8a0dc3a18)

@laurent

Or you can try disabling all plugins temporarily to see if it makes a difference using safe mode (also under the Help menu)

This is what I did, and the sync is in progress. I wait for it to finish to see if it restarts again afterwards:

EDIT: safe mode sync ended after several minutes:

And here are the last lines displayed:

14:32:09: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local 5a647c39d5a13d9c0ce453405a1480fe)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 14:32:11: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local dd43b8411a6c2707e603403f690a137d)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 14:32:12: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local d179dc2eab0920accfb431dab4037a7f)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 14:32:15: Synchronizer: Sync: createRemote: remote does not exist, and local is new and has never been synced: Resource: (Local bb0194329a31a0a006f33ca22828cadf)
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 14:32:19: Synchronizer: Processing a path that has already been done: efd8946836fb499d9d2cd2130f9efd7f.md. sync_time was not updated? Remote item has an updated_time in the future?
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 14:32:19: Synchronizer: Sync: finished: Synchronisation finished [1713267956461]
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 14:32:19: Synchronizer: Operations completed: 
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 14:32:19: Synchronizer: updateRemote: 1
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 14:32:19: Synchronizer: createRemote: 2800
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 14:32:20: Synchronizer: Total folders: 209
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 14:32:20: Synchronizer: Total notes: 16453
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 14:32:20: Synchronizer: Total resources: 95989
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 14:32:20: checkDisabledSyncItemsNotification: No errors: Hiding notification
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 14:32:21: Sync has finished and note has never been changed - reloading it
C:\Users\nonob\AppData\Local\Programs\Joplin\resources\app.asar\node_modules\@joplin\utils\dist\Logger.js:221 14:32:22: DecryptionWorker: cannot start because no master key is currently loaded.
DevTools failed to load source map: Could not load content for file:///C:/Users/nonob/AppData/Local/Programs/Joplin/resources/app.asar/index.js.map: Unexpected end of JSON input
DevTools failed to load source map: Could not load content for file:///C:/Users/nonob/AppData/Local/Programs/Joplin/resources/app.asar/AsyncActionQueue.js.map: Unexpected end of JSON input

I see this line, maybe a clue:Processing a path that has already been done: efd8946836fb499d9d2cd2130f9efd7f.md. sync_time was not updated? Remote item has an updated_time in the future?

I then just press Synchronize to see if it ends immediately, well no, here we go again for remote objects created:

In the Joplin options, the modules are always indicated as activated, but I imagine that this is not to be taken into account, that they must actually be deactivated in safe mode...

@roman_r_m

Maybe try disabling sync by setting sync target to None...

I'll try it when the current sync is finished. Can I then resume synchronization by restarting WebDAV or will everything be started from scratch?

And isn't the "Frequency sync" setting supposed to completely disable sync when it's set to "disabled"?

@roman_r_m

...and see if the slowness is still there. If it is, it may be due to a plugin.

It's only when I have a backup or synchronization in progress that Joplin is very slow, other than that it works well. There it is in safe mode with synchronization in progress, it's not as slow as when I have the problem in normal mode, but it's not very fast either.