Linden Lab have been having a ton of technical difficulties with Second Life lately. More this week than I can remember anytime recently. The backbone is overloaded again, apparently, but it's hard to give you any useful concurrency numbers to go with.
You see, the concurrency maxed out at about 8:50am SLT (US Pacific) and stuck there. Oh, Linden Lab are reporting concurrency zero more often than not, but when we are getting a figure it's been between 34,104 and 34,561 all day. Basically the numbers suddenly plateaued.
At least when Linden Lab is reporting zero concurrency, you know that's breakage you can trust. This? I don't know what to make of this. It's easy to blame the data feed, but it's showing variance between samples, rather than repeating the same numbers over and over, as if the grid really were capping out around 34,000.
It looks like login numbers are being capped, but it could just as easily be that the numbers being reported by Linden Lab are garbage.
1. there is the possibility (even if small) that something like grid performance or somthing was helping balance the concurrency, some people joining and leaving, some people staying and some people logging after staying for a while
Posted at 1:04PM on Jun 16th 2007 by TigroSpottystripes Katsu