Evaluate the causes of the slow-down related to heavy project

What's an heavy project:

• size in mb
• commit log size
• old forked branch
• use of massive revert

On all different save step:

If you're using the advanced mode (a few users):

• Check access to the project
• your changes are send to the server
• it updates a local clone which is most of the time just reset (cloned if you're in studio for the 1st time)
• it updates the files on your workspace's branch (dedicated to your user and the branch you are working on)
• it commit the changes
• it updates all local caches
• it propagates asynchronously the update event on the cluster: any node which handle the given project may update the cache
• Studio validation

If you're using the simple mode (default mode):

• Check access to the project
• your changes are send to the server
• it updates a local clone which is most of the time just reset (cloned if you're in studio for the 1st time)
• it updates the files on your workspace's branch (dedicated to your user and the branch you are working on)
• it commit the changes
• it updates all local caches realted to the updated project
• it propagates asynchronously the update event on the cluster: any node which handle the given project may update the cache
• it merges your changes to the common branch
• it push the changes (unless there are conflicts)
• check the common branch (i.e master most of the time), if there are some pending commits to pull but no associated changed files, pull the commit (that's a merge in my favor)
• it updates all local caches realted to the updated project
• it propagates asynchronously the update event on the cluster: any node which handle the given project may update the cache
• Studio validation