Nostalrius Begins - Quality wow vanilla realm (1.12)

I've been looking for a post to voice my concerns in, but have been unable to find any. I guess that means I'll have to make one.

I am growing increasingly worried that we'll have to wait for the arrival of clustering, before we can reliably complete a raid before the server crashes.

This trend only started on the 24th of febuary, so I suppose I'm jumping the gun a little here, but surely I'm not the only one who's frustrated and worried by these frequent crashes. It's natural that the server cannot handle 12,000 clients logged on at the same time, but reliably crashing midraid with 40 players having collected worldbuffs only to immediatly lose them because of server instability is extremely detrimental to the atmosphere of the raid.

Things you can do:
1. Reschedule the raid if 12k people are on
2. Don't schedule raids during "primetime"
3. Wait until clustering (no eta so that could be a while)

the server isn't exactly unstable. Especially after updates crashes will naturally occur.

The population however only is a very minor factor to the amount of crashes.

XxGokuxX wrote:Things you can do:
1. Reschedule the raid if 12k people are on
2. Don't schedule raids during "primetime"
3. Wait until clustering (no eta so that could be a while)

Yeah we'll all quit our jobs and/or studies and raid at 7 in the morning.
You know why primetime is when it is, right? There's a life beyond wow, I know it's shocking, but it's true. People get off work, off school, done with dinner and then they log on to play. If the server is up. Simply not raiding until clustering is done is not really a solution either. It could take months.

Any ideas that don't involve unrealistic circumstances? I'm all ears.

Mad

edit: apparently the question was deleted, well... I'll leave the answer up anyway

proper scripting, what else?
the more players a server has, the higher is the probability of someone running into a crash source.

However with such a huge population this will only have a noticeable effect shortly after an update.
High population actually is a plus factor to stability when it comes to identifying crash sources.
Blizzard with hundreds of servers could easily take advantage of this; whenever a server crashed, the fix was applied to all other servers, resulting in a high stability.

Thefilth wrote:

XxGokuxX wrote:Things you can do:
1. Reschedule the raid if 12k people are on
2. Don't schedule raids during "primetime"
3. Wait until clustering (no eta so that could be a while)

Yeah we'll all quit our jobs and/or studies and raid at 7 in the morning.
You know why primetime is when it is, right? There's a life beyond wow, I know it's shocking, but it's true. People get off work, off school, done with dinner and then they log on to play. If the server is up. Simply not raiding until clustering is done is not really a solution either. It could take months.

Any ideas that don't involve unrealistic circumstances? I'm all ears.

What did you expect? You can either accept the problems that come with raiding when everyone else likes to raid or you can change your schedule. I'm sorry you can't afford good Internet/have a shitty job and you DC all the time, but these are the types of answers you get when you make a post to bitch and moan

What is the point of this thread, besides stating the obvious? It doesn't bring anything to the table.
All we can do is hope the clustering solution will fix it.

It isn't an ideal situation, but not wasting time on world buffs if you're guaranteed to lose them is a no-brainer.