We have our asset server on an independent machine that does nothing else. After checking in a new project we’ve noticed that it takes between 60-120 seconds (at least!) just to get a response from the asset server working with this new project. Once the server responds, it doesn’t seem to take any time for it to transfer files back and forth or tell me what is new/changed either locally or on the server, but the time it takes to respond is ungodly. Of the projects checked in I’m working with, project A is composed of 2.49 GB of data in 4,147 files, while project B is 2.32 GB of data in 25,274 files and it’s the project B that’s choking for response.
So my question and problem is regarding what is being done during the time my machine is ‘waiting for a response from asset server’? Is each time the server is contacted (whether because you switched to the server tab, are committing a file, are updating from server, or refreshing server view), is the asset server forced to go through checking and comparing all it’s assets and metadata? Is there any way that can be changed/optimized… I’ve never experienced anything similar when using CVS or SVN. Thanks.