Improve Mutagen Sync Efficiency For M2 #607
Replies: 3 comments
-
I definitely agree that initial synchronization is way too slow. I don't think one-way sync here works as a general purpose solution, though. For example, I often insert debugging code in That said, I don't understand why mutagen initial sync takes so long. I reckon an rsync would be faster at this point, so I have to wonder what's really going on - and/or if its a bug with Mutagen |
Beta Was this translation helpful? Give feedback.
-
@navarr good point on the vendor use case. I haven't needed to modify anything like that since i've made the change, but that is something I have done in the past from time to time. |
Beta Was this translation helpful? Give feedback.
-
A follow-up for me, specifically, I had an antivirus with real-time file protection which was slowing sync down by 15x at least. |
Beta Was this translation helpful? Give feedback.
-
The biggest hangup I am experiencing using warden is the time it takes to complete the initial synchronization. I have added the following to my .env file to help:
WARDEN_SYNC_IGNORE=vendor/**,var/**,pub/static/**
With this setting, I need to run all of my composer commands in
warden shell
and then run acomposer install
outside of warden so I can debug--not ideal but workable.I have to imagine that the
generated
directory is also causing the sync process to be slow, but I cannot work around having that sync back to my local.I'm wondering if it would be possible to have some directories sync using mutagen's
one-way-replica
mode to improve sync time.Beta Was this translation helpful? Give feedback.
All reactions