Why does UAS sometimes take a very long time to cache very little?

Questions & Answers
1

When using Unity Asset Server (UAS), this is the situation that occurs occasionally:

  • check for changes
  • update from server
  • work a bit
  • check for changes
  • update from server
  • work a bit
  • check for changes - takes 15 minutes to re-cache

i.e. I am almost entirely in-sync with the server, and then instead of just quickly checking if something has been updated, Unity is unusable and I have to stop working. Just now when this happened it came back with a grand total of 3 files changed.

I'm guessing it is rebuilding/re-downloading the entire project history (since I'm less than 30 minutes / 3 commits out of sync). What is going on that is making UAS think I need to do this, and how can I stop it?

2

Im having this same exact issue! Its extremely frustrating. Sometimes I have to sit and wait for almost 20 minutes for Unity to respond. Does anyone know what is going on and is there anything I can do to shorten or get rid of the wait? I dont remember having this issue ever in 3.2 or 3.4.