Lag may have a clue to zone DC

[Emili]

So... I had just logged through five characters.

I walked into house C and of course ...

Zone DC

What was interesting this time is that the aerver been very laggy all day... so very slow server response.

What I noticed was -> Five consecutive separate Load screens to house C as if the system was attempting to load an instance for each character I previously had been logged on to.

[deahamlet]

It's well known that if you swap toons too much DDO becomes laggy no matter what.

[Daggertooth]

Everytime you load a zone you load up more memory onto your RAM. DDO used to purge your RAM as you went as I never ever DC'ed from the game for the first 4 years of playing. Approximately 2 years ago, something changed in that now your RAM file just continues to build up bigger and bigger. Loading large zones like the desert, the fens, the orchard etc have a bigger chance of causing the instability that will cause you to DC and get the error. If you open up the task manager and look at the page file you can see how much memory is being used. If you have over 1 GB of memory being used (i.e. it says something like 900,000 kb or 1,100,200 kb and you go load into the desert or fens or something I can pretty much guarantee without fail that you'll crash and DC. Im 99% sure that DC'ing has nothing to do with anything coming from the server. The problem is that instead of purging stuff you did an hour or two ago, it is now just continuing to hold it in memory thus making your page file bigger and bigger to the point of inevitable instability. If DDO purged the memory file of stuff you ran an hour or two ago and the page file never went over 500 or 600K like it used to, no one would ever crash/DC loading in anywhere.

[Emili]

Everytime you load a zone you load up more memory onto your RAM. DDO used to purge your RAM as you went as I never ever DC'ed from the game for the first 4 years of playing. Approximately 2 years ago, something changed in that now your RAM file just continues to build up bigger and bigger. Loading large zones like the desert, the fens, the orchard etc have a bigger chance of causing the instability that will cause you to DC and get the error. If you open up the task manager and look at the page file you can see how much memory is being used. If you have over 1 GB of memory being used (i.e. it says something like 900,000 kb or 1,100,200 kb and you go load into the desert or fens or something I can pretty much guarantee without fail that you'll crash and DC. Im 99% sure that DC'ing has nothing to do with anything coming from the server. The problem is that instead of purging stuff you did an hour or two ago, it is now just continuing to hold it in memory thus making your page file bigger and bigger to the point of inevitable instability. If DDO purged the memory file of stuff you ran an hour or two ago and the page file never went over 500 or 600K like it used to, no one would ever crash/DC loading in anywhere.



It's well known that if you swap toons too much DDO becomes laggy no matter what.

I know DDO has terrible garbage collect... memory leakage as we call it. Fact is you do not HAVE to do anything on the character just swap between them seconds apart.

What I am saying however is it is looked more pronounced at x character swaps due instead the objects for ONE instance being sent down to the client ... it looked like I got the objects for x(Character swaps) instances being sent to the client.