Server Population
Posted: Mon Jan 23, 2006 3:56 pm
Finally, blizzard has listened to us, (my server at least).
http://forums.worldofwarcraft.com/threa ... ost6752032
http://forums.worldofwarcraft.com/threa ... ost6752032
WarcraftRealms.com
General Forum for WarcraftRealms.com
http://162.254.149.72/forum3/
Server Population
Page 1 of 1
Posted: Mon Jan 23, 2006 5:52 pm
thank **** dog
Posted: Mon Jan 23, 2006 6:51 pm
But they still didn't close new char creation on Bloodscalp which is always queued when I try to log in =/
Posted: Mon Jan 23, 2006 9:17 pm
how long was your queue typically rollie?
last night when i tried to log into Doomhammer we had a 24 minute queue then an additional 10 minutes for the char select screen to load. by the time you actually logged in you were AFK and sitting down.
totally NOT kidding or exaggerating. its been hell. ive had a few guildies say they will not renew unless this changes.
last night when i tried to log into Doomhammer we had a 24 minute queue then an additional 10 minutes for the char select screen to load. by the time you actually logged in you were AFK and sitting down.
totally NOT kidding or exaggerating. its been hell. ive had a few guildies say they will not renew unless this changes.
Posted: Mon Jan 23, 2006 10:00 pm
0 min queue last night, about 3 min at char retrieval, and another 3 logging in.
I don't know why my server says they have issues. But luckily, we're one of the few closed.
I don't know why my server says they have issues. But luckily, we're one of the few closed.
Posted: Mon Jan 23, 2006 10:27 pm
Look closely at the list, it's not the highest population servers, it's a mix of highest pop servers and servers with stability issues. Icedown, Mal'Ganis etc. are servers that have had severe stability issues and have been down days at a time with database integrity issues. Reducing changes to one of the most accessed and important tables is a good way for the database admins to be able to run some extra diagnostic and try and sort out the issues... Though in truth on a farm this size the way to do it would be new hardware and rebuild the data on the new hardware, eliminating both HW timing issues and rebulding the database indexes to reduce inherited flaws, but I have a feeling they don't have a backbone structure that allows that kind of thing with limited downtime.