Lag and Server Instances

seph1roth5

Well-known member
So I keep hearing people say how bad lag is at peak playtimes, when population hits 900+. Now I think this is definitely contributing to the lag, but I think there's something else going on behind the scenes.

I know people are pasting their /loc of super lag, and I had recommended to Cordo that he make a thread keeping track of all that, but don't think it's happened yet. What I started doing a week or 2 ago is keeping track of all of my instances. The bad ones all had severe lag multiple times. The good ones had none of this "new" lag and just typical lag I remember from Orien. Such as a 4-5 sec burst at the end of some cogs quests. Some I put in the middle, where there was no lag until the end fight or a particular part of a quest.

When I run quests (other than impatient pugs), I hop in, /loc, and check my list. If it's an instance that's been horrible before, I leave and reset it. So far that's been VERY dependable. There was 1 server I had on my "good" list that later on had a bunch of lag, but I chalk that up to mistakes in my notes. It probably had a bit of lag but I thought it was negligible so didn't note it.

I don't know how instances in DDO work exactly. I know in the past devs have mentioned some things like guild airships were typically on a different one. Maybe they're bundled? Maybe 11, 25, 44, and 56 are all connected, and are also bad? No clue. Maybe instances 33, 45, 46, and 47 also handle reincarnation cache and pets? Also not sure if it's separate based on our actual servers. I'm on Shadowdale.

I've noticed whenever a public area is having an aneurism, it's been one of the server #s from my bad list too. I'm going to list my stuff here, and if anyone wants to put up their /loc too, that would be helpful. But only if it's this new 64 bit lag, which can often look like old 32 bit lag, but I've noticed some differences:

1 - Party chat and user chats aren't affected at all. Everyone can chat just fine but can't connect with monsters (maaaaaybe 1% of the time), movement is janky, enemies can still hit you. /loc takes a long time to register, as do party invitations and PMs. (not sure about guild chat, my guild is only 4 of us and we use a userchat instead)

2 - Lasts FAR longer than normal. Took me 10 min to get from the gingerbread golem in feywild to the bear. (I know orien would sometimes have big lag too but even thunderholme and raids were never THIS bad, and chat was affected then)

3 - Frequently pops up in scripted events. Such as plantzombies coming out of pipes in cogs, or abishai portals appearing in myth drannor. Gnomon/drow at the end of lords of dust, etc. Sometimes a quest will seem fine and then you get to one of those parts and are slammed for 5-10 min.


I'll try to update my list with other people's stuff, but again I'm looking for big big lag, 5+ min, with chat being normal, and anything else newish people notice. Not just some rubberbanding, or locking up for 30 sec, like when you get to the end chest of a quest kind of thing.

Very bad instances: Usually takes longer just to load into the quest, never a good sign.

11, 13, 14, 15, 17, 18, 21, 24, 25, 32, 33, 37, 41, 44, 45, 46, 47, 49, 52, 56, 57, 61, 64, 66, 68, 73, 76

Questionable ones: Ones that were "mostly fine" and only had some lag at 1 or 2 points. Maybe not QUITE as bad as the ones on the bad list, but still more than normal 32 bit orien stuff. I'm thinking it might've been more simple quests, and these instances on a more complicated one will be a dumpster fire.

12, 15, 31, 42, 48, 51, 54, 55, 78


Good ones: No new lag noticed when I ran these, some multiple times. Maybe a few sec of lag here and there.

16, 22, 23, 26, 27, 34, 35, 38, 43, 48, 51, 53, 55, 58, 62, 63, 65, 67
 
Last edited:

Pilgrim

Well-known member
just in case this is server specific you should include what server your on.

EDIT: might also mater if your solo/full group/raid. No idea however.
 

seph1roth5

Well-known member

Steel talked about it a bit on discord the other day. From what other people said later though, he may have been talking about the instance # specifically, like i2004. I was using instance in the more broad term to describe the map that it makes for you and your party, the one you can reset.

Still, strange that your 51 was so bad though. That's also a SUPER scripted quest though, with an npc. So maybe the few times I had 51 it was a simple thing where any lag was just a sec, but in an Ana quest there's like 50,000 more things going on. I'll keep an eye out for it.
 
Last edited:

kobra492

Member
commenting for awareness and also adding i've ran raids all day and some raids like hunt or hunted, and also ton are extremely laggy regardless of server number. however it does seem lower numbers feel better in general and a server run of 48 or 50 for hunt or hunted vs 17-24ish at the max is night and day different it feels like areas with tons of mob spawns it locks up the entire raid and forces wipes, numerous ones. also ran deathwyrm and had the same issue of it legit wiping and locking up people are sick and tired of it.. myself included. for reference my latest ton raid that i scouted and still ended up lag locked for 35+ minutes and having someone leave.

(Standard): You are on server 17 at r2 lx824 ly8 i2052 cInside ox-19.23 oy33.61 oz-249.95 h154.7. Game timestamp 10492758.276.
OajyrE5.png
 
Last edited:

Jasparius

Well-known member
Hall of Heroes on Thrane is server 62 and I cannot move. Logged out and in again, still lagged and cannot move.

I dont think it is server instance. I think the game is just garbage at the moment.
 
  • Like
Reactions: DBZ

An den

Well-known member
Hall of Heroes on Thrane is server 62 and I cannot move. Logged out and in again, still lagged and cannot move.

I dont think it is server instance. I think the game is just garbage at the moment.
It's not the server instance. Whatever is going on with a particular server instance at a particular time / day would not persist through a restart of the servers. One day an instance could be fine the next horrible. This whole thing about instances really took off with the invention of HC servers and then Cormyr. Its just not accurate.

The troubleshooting the OP has done is comparable to someone trying to puzzle out why a lamp does not work but not understanding that it is a lamp or what a lamp even is.

Well done but a complete exercise in futility.
 
They posted a long post about Memory leaks and garbage collection background systems and server side problems they plan to address in this weeks upcoming update to some degree.
 

An den

Well-known member
They posted a long post about Memory leaks and garbage collection background systems and server side problems they plan to address in this weeks upcoming update to some degree.
Well I hope they fix it. We are at 55 days and counting now and the user base here is going down rabbit holes in an attempt to troubleshoot the issues for them. sigh.

I bill people for services rendered 30 days AFTER I do the work. That is standard in the US. Here we have the reverse where we pay upfront for a service and we are almost at 2 billing cycles later and its still borked.

I stopped paying them.

Although I really like the game and have been loyal for a long long time it's just become a farce.
 

waysider

Well-known member
Stuck right now in Clifftop

(Standard): You are on server 14 at r1 lx1578 ly1881 i13 ox47.85 oy36.12 oz653.44 h347.3. Game timestamp 5829008.087.

mm but then was alright on a server 64 run
 
Last edited:

Thau of Blackmoore

Well-known member
Shadowdale - Sharn/Cliff top Quest Entrance: (Standard): You are on server 14 at r1 lx1580 ly1880 i13 ox84.43 oy13.84 oz653.43 h344.5. Game timestamp 5830148.703.

Lag
 

seph1roth5

Well-known member
You could have led with this and saved a LOT of typing. The number is meaningless. The load on the CPU from the server and platform related activities as well as level of DB contention are all that matter and /loc is not going to show that.
More accurate is that NO one knows how the instances work, even the devs lol. But again I'm using instance to just describe the dungeon/wilderness/whatever map being made for the people in it, not the specific i1056 kind of thing.

I started MMO-ing on Ragnarok Online, where they didn't HAVE multiple instances for the longest time. Each map was just a one-off, so if you wanted to go level in nibelheim, and 200 other people did too, you were ALL there. Great if you were strong enough to handle the monsters respawning on your face, but otherwise...Eventually, RO developed a rough instance system for short quests/events. You'd talk to an npc and go into a waiting room of sorts (basically just an in-game chat room) and then when enough space was free you'd be zapped in. But even then, they would only have like 4-5 different instances that could be used.

Like I've mentioned, I don't think it's 100% the server #, but there seems to be some kind of correlation. Whenever I'm partying w/ my group, and the first person in takes more than a few sec to load into a quest, we know it's going to be a crappy instance. Once 10+ sec has passed we know for sure. And when they fiiiiiiinally load in and do /loc, it's never been a # off our good list, and has always been one off the bad or one we haven't checked before. So we reset until we get a non-bad one and it works 10000x better.

This also isn't dependent on prime time, I've had the same results at 1am on shadowdale. I joined someone's death house the other day. They had been in there for 10 min and were just lost wandering around the first area, before the dollhouse/door. They were new to RL so I told them to meet me at the top of the stairs. Took me about 3 min just to walk up there from the entrance, and he was having trouble too. I had /loc'd and it was on my list O crapservers, so I told him let's reset. We did, got a better #, and the thing went smoothly.

I've also had it take a while to load into a quest initially and gotten like 4-5 bad servers in a row. All took a good 30 sec to load in, if not much more. Maybe some quests just have more crap going on at the start? No clue.

Maybe it's just all superstitious like winning a football game twice in a row with the same pair of dirty socks on, so now you always wear those socks. But this system seems to be working pretty well for me. I hear people talking about wiping during primetime and being stuck in place for 10-15 min all throughout the night, and my group spends maybe 2 extra min an hour checking/resetting instances, and then 95% of our quests run smoothly (sometimes we test a new # and it turns out to be bad).

Not much we can do when a PUBLIC instance is a bad # and super laggy though. Just keep trying to tele out over and over until it works. But once we finally get out of that we're good.
 

waysider

Well-known member
Not much we can do when a PUBLIC instance is a bad # and super laggy though. Just keep trying to tele out over and over until it works. But once we finally get out of that we're good.
I agree that we don't know anything for sure, but that includes we don't know for sure the server #'s aren't part of it. Note the "server 14" problem in Clifftop Wednesday night (see above).

Busy public areas like Clifftop don't clear out very often, and if the the "garbage loop" thing strikes and freezes the instance, it can last for ages as people zone in there frequently. (and they were stacking up at the zone in point Weds Night)

It sure looks like it's more of a "garbage loop" thing than that it's overall processing load. Sure, auras and pets are still there, but compared to raid moments there's less process going on and instances still freeze up.
 
Top