coppro wrote:
Also, you could close all the other databases temporarily while performing the room upgrade, since it's the biggest RAM-hog.
Actually, this is probably unhelpful. When I've profiled memory usage, I've confirmed that opened .dats only allocate RAM for parts of them that have been accessed and modified in the current session. Though the other .dats are open, they populate negligible RAM during the upgrade routine, especially if upgrade is rerun after an incomplete procedure. If you profile the app and can show evidence that memory usage is substantially reduced (i.e. by more than a couple MB) by closing the non-participating .dats during upgrade, then I'll consider optimizing it.
P.S. Interestingly, Jatopian's .dats already had the room data upgraded successfully when he handed them off to me, so that part of the procedure isn't a problem for his system, evidently. Curiously, it was the final step of transferring the player data that he was stuck on.
____________________________
Gandalf? Yes... That's what they used to call me.
Gandalf the Grey. That was my name.
I am Gandalf the White.
And I come back to you now at the turn of the tide.
[Last edited by mrimer at 10-01-2007 04:42 PM]