It is query time. The team that built the cube,would load data into the cache and use it all day long. But now MS will clean out cache items that have not been used for 30min. However I think that is due to bad cube design, but I need info about where the deadlock is. Looking at the server the Processor, memory,and Hard drives all are between 40% and 65% avg... even looking at spikes there is still 20% or more left.
I wonder if there is a problem with seek times on the hard drive, but looking at this from the SQL server side... there isn't any issues..So I need some way to tell what is creating the delay in processing a query in the cube.