01-17-2007 20:09
Posted initially on 1/15. Since there seems to be no concept of answering questions in the order they were asked in this forum, I'm assuming my post has been skipped since questions posted since then have been answered. So I'm reposting in hopes of actually having my question answered. (Crazy expectation I know!)

The definition of the verb 'resolve' with which I'm most familiar is "bring to an end; settle conclusively."

When problems stemming from load are posted to the Official Linden Blog, the posts are later marked as "resolved" when the concurrency falls below the problem point of circa 21,000 concurrent logins.

LL knows, and the technically savvy amoung the user base (most of us) knows, that load problems are here to stay until something significant is done, in the short term, to alleviate the problem, such as only allowing paid accounts to log in after the concurrency hits 18k or so. Redesigning the gridware to better handle communication with the DB will take a long long time to truly resolve the load problems.

So, why do the grid monkey's keep using the word "Resolved" in the blog when we all know the problems have merely abated for the moment until the next concurrency spike?

Is it possible to switch to a more accurate phrase like 'problems subsiding' or 'the storm has passed' or something a little less finite and inaccurate than 'resolved'?

If you must stick with such an inaccurate phrase, could you please explain to the rest of us what definition of the word 'resolved' is used at the LL offices? Because it is apparently a definition that the rest of the english speaking world is not familiar with.

(this is only mean to be partly sarcastic, the question is valid in the face of constant misuse of the word.)