If you are wondering why a document suddenly takes more than 6hrs to reload, there is an easy technique to find uout why this is happening:
Take two Document Logs, one from a manual reload or a reload on another machine (a "good" reload), and one from a reload that is being killed because of taking more than 6hrs to complete (a "slow" reload), and open them side by side (for example in Notepad++ or another text editor that can open multiple files). They should list the same sequence of instructions, but the instructions will have different delays.
Check the start time at the top of each log file, and navigate down while keeping the two files in sync. The instructions in your log file of the slow reload will gradually - or all of a sudden - start to take excessive amounts of time to complete. Or maybe it's the last instruction that never seems to finish in one log file, while in the other it completes within a reasonable amount of time and proceeds to the next instruction.
That's where you should focus your attention. Why is this happening? Too many reloads in parallel? QVS eating up all RAM on the slow machine and as a result not enough RAM left for a decent reload?
