Complete rewrite of the Looking for Group system my ass

rollingphoneseb17_ESO

"We’ve already had to make some adjustments to this on the live servers in the week after Update 24 went live to fix some performance-related problems.It is now functioning well and is holding up to the player load, but we have already found a few ways we can make the system better and will be doing additional work that should be completed before Update 25 launches."

WildRaptorX

Didn’t know we could say ass

rollingphoneseb17_ESO

Forums functioning just better.

rollingphoneseb17_ESO

Their fixes should be fixed as it seems, but not entirely and perhaps never actually will be fixed.

nafensoriel

rollingphoneseb17_ESO wrote: »

"We’ve already had to make some adjustments to this on the live servers in the week after Update 24 went live to fix some performance-related problems.It is now functioning well and is holding up to the player load, but we have already found a few ways we can make the system better and will be doing additional work that should be completed before Update 25 launches."

Rewriting the code is not the problem. Making your new system work with everything else is the problem.

Shantu

If there's an ass involved in this, it's the metaphorical one owned by ZOS that's getting kicked.

It's a typical developer syndrome to over-estimate the readiness of your work. Unfortunately, no matter how well developers think they have fixed an issue, there is no way they can duplicate the stress created when going live. Mistakes will made. That's just the nature of the business...and life, for that matter.

Goregrinder

nafensoriel wrote: »

rollingphoneseb17_ESO wrote: »

"We’ve already had to make some adjustments to this on the live servers in the week after Update 24 went live to fix some performance-related problems.It is now functioning well and is holding up to the player load, but we have already found a few ways we can make the system better and will be doing additional work that should be completed before Update 25 launches."

Rewriting the code is not the problem. Making your new system work with everything else is the problem.

Yeah it's like trying to join a Mac to a Windows domain or active directory. It's not simple.

FierceSam

Shantu wrote: »

If there's an ass involved in this, it's the metaphorical one owned by ZOS that's getting kicked.

It's a typical developer syndrome to over-estimate the readiness of your work. Unfortunately, no matter how well developers think they have fixed an issue, there is no way they can duplicate the stress created when going live. Mistakes will made. That's just the nature of the business...and life, for that matter.

Agree 110% about over-cocky programmer syndrome (and the people we’re talking about here are programmers, not game developers). Except stress testing is exactly one of those things you can do outside the live environment before you commit to going live.

Understanding load and the effect of multiple calls on a system is precisely the sort of thing programmers should be doing before going live. And I’m not talking about p*****g about on PTS with 2 dozen players and pretending that is testing your system. I’m talking about serious backend testing that actually mimics the activities of, say, twice your maximum projected audience all doing stuff at the same time. Then seeing how it copes with 10 times the audience. That is exactly what you can do to ensure that this type of event doesn’t happen in future.

I suspect ZOS haven’t really invested enough time, money and effort in this area if a part of the PC EU playerbase can bring down their megaserver in 30 minutes.

SeaGtGruff

We can say "ass," but only when it means one of these:

https://4.bp.blogspot.com/-BmT-BqaBEPI/Wnuft96XaLI/AAAAAAAAB-o/WIr-Wl_klOMBg89dF1Dn6wzhN7CbZjmDwCLcBGAs/s1600/DSC_0376.JPG

Goregrinder

Shantu wrote: »

If there's an ass involved in this, it's the metaphorical one owned by ZOS that's getting kicked.

It's a typical developer syndrome to over-estimate the readiness of your work. Unfortunately, no matter how well developers think they have fixed an issue, there is no way they can duplicate the stress created when going live. Mistakes will made. That's just the nature of the business...and life, for that matter.

Someone who understands that you can't even guess stress loads on systems until you actually deploy it. Did you go to Sensible High Schools or something?

[Deleted User]

Hello there,

With this thread not opening very constructively, we're going to go ahead and close it down. For further posts be sure to stay constructive with the Forum Rules in mind when giving opinions to avoid thread derailment.

Thank you for understanding.