Slow client sync on large library

Not sure if this is a Client issue, or an issue with notify_push

I assume that when a file is modified, in server, it notifies the windows client to download that file
"Hey Windows Client! File ABC was just created or modified, please sync it"

I have a storage library with over 200.000 files, and the windows client is really slow to sync these updates.

I believe that instead of just update the "ABC" file, it is checking for changes on all library before update it.
It takes a long time in "Syncing changes" and "Checking folder changes" , which makes syncing really slow.
Assume that you modified 10 files in sequence.
The windows client will receive 10 push notifications and will check for changes in file library 10 times.

The push notification isn't supposed to notify only about what changed?
Should it not just sync the "ABC" file directly?

The issue happens both ways.
If you rename a virtual file on explorer, it takes a long time before you be able to open the file.

Start by reproducing the delay with a large library and tracing how notify_push handles successive Windows client notifications. Compare the "Syncing changes" and "Checking folder changes" behavior for individual updates and renames. Done means changed or renamed files sync without redundant full-library checks.