Jump to content

Sparks

Administrators
  • Content count

    40
  • Joined

  • Last visited

About Sparks

  • Rank
    Sysadmin of Ice and Fire
  • Birthday May 17

Profile Information

  • Gender
    Female
  • Location
    Seattle, WA

Previous Fields

  • Name
    Rachel Blackman

Recent Profile Visitors

3,441 profile views
  1. Sparks

    Board Issues 4

    (Having everyone involved out-of-town the Monday after the first episode was, sadly, not ideal! Pesky offline life considerations.)
  2. Sparks

    Board Issues 4

    Okay, mail should be working again. Sorry about that!
  3. Sparks

    Board Issues 4

    There send to be a problem with sending email; Ran and I will look into it.
  4. Sparks

    NBA Finals: TRILOGY Edition!!!

    Sorry about that. Traffic was low enough that it seemed the best time to do the database migrations.
  5. Sparks

    Server Move

    We had a replication error when I first turned everything live again, so I took us down to do a rebuild of some database data. But we should be good to go now.
  6. Sparks

    Board Issues 4

    Okay, no, sorry. There was a replication error I had to solve. NOW we're up and running properly.
  7. Sparks

    Board Issues 4

    And as a followup, we now have a replicated database here on Scramble (the new server), and it's up and running fine. Hopefully everyone will find things a little more zippy now. There is also a test copy of the wiki running on Scramble, which I'll leave up to Ran as to whether or not we move everyone to that one eventually. Scramble has enough oomph it might be able to take on everything.
  8. Sparks

    Server Move

    We are now running a replicated database across two servers, which should be a little zippier. The forum is still horribly ungainly, but it should be slightly less egregiously slow now.
  9. Sparks

    Server Move

    Just to add to this, as of last night, we're on the new server. We're slowly turning things back on, to make sure we don't break anything along the way, so you should see performance pick up as we do so.
  10. Sparks

    Board Issues 4

    We're moved onto the new machine in preparation for the season. I will probably be tuning and tweaking things over the next few days, so bear with me and call out to me or Ran here if things break.
  11. Sparks

    Can Only View a Handful of Past Posts?

    (Emphasis mine.) I take care of the servers; board administration is Ran's bailiwick. However, I believe that Ran has moved a lot of older and inactive threads out of the active boards, during the time we were trying to shave the forum's resource use down. So if those posts were in threads that had not been touched in several years, they've probably been stuffed into archives instead. Ran, can you elaborate?
  12. Sparks

    Board Issues 4

    If it's happening to you multiple times a day, there there is a known bug with Invision (the forum software we use): if you have an old Invision login cookie around and a new one, you'll potentially get logged out during certain operations. I had blocked that bug before by having Varnish eat old Invision login cookies (so even if you had one, the board never saw it), but with our move to nginx I couldn't do quite the same filtering. That might be the cause. The fix is just to clear your westeros.org cookies out, and then log back in again.
  13. Sparks

    Board Issues 4

    That's not a 'Board Issue' per se—i.e., something not working right/broken on the board itself—so probably could've gone in a separate thread in the forum. That said, changing your signature is fairly straightforward. Just go to the Account Settings page (which is also available from the little dropdown that pops off your name, from the top of the board), and select Signature from the list on the left-hand side. Et voila, an editor to change your signature!
  14. Sparks

    Board Issues 4

    Ugh. I hadn't noticed that nginx blocked path-type URLs. I've added some rewrite logic which hopefully fixes things.
  15. Sparks

    Board Issues 4

    As background, think of the forum and wiki like a ride at Disneyland. You can only have a certain number of people on the ride at a time (i.e., the maximum number of PHP instances), but you can have a larger number of people waiting in line for the ride (the pending connections). Some people are okay just watching a video of the ride (Varnish cache for non-logged-in users), and so they can come to the end of the line, watch the video, and leave. Others, however, are stuck waiting for a space on the ride. That long delay before the page starts loading, that's the waiting-in-line part. As soon as the page starts loading, that's you actually being on the ride; you can see that the latter part has gotten considerably faster, but less so the first part. Now, there are two factors that determine how quickly that line moves: the speed of the ride (i.e., the server's CPU capacity) and the number of people you can fit on the ride (i.e., the server's RAM capacity). The faster the ride goes, the quicker you can get people back off and get the next group on. The more people you can fit on per run, the bigger a chunk of the line you can take away each time the ride comes back to put new people on. When the line gets gummed up, that's when things go wrong. Too many people in line, and the amusement park staff cap the line and refuse to let anyone else get in. (That's the 500 error you get sometimes.) Enough of those 500 errors, and Cloudflare itself marks the site offline. So, clearly, we need to keep the line from getting too long, and not just for performance reasons! But what if we just, I dunno, crammed more people in the ride? Those safety guidelines are for wusses, right? Well, turns out, if we risk that, that's when we hit the server's RAM limits. Lots of page faults, and the processors become bogged down, and we end up in the death spiral. People flying off the ride screaming, things on fire, things turning just generally Not Good. That's the part where instead of the server recovering on its own, I get back to the keys and have to try to balance things (or Ran just shuts things off until it recovers). Now, previously, the Wiki and Forum were two tracks of the same ride; they shared capacity and the line waiting to get in. This obviously wasn't ideal. We've split them onto two separate servers—made them into separate rides—with separate waiting lists and separate capacity. There's still some shared resources (notably the SQL database backing it, off on a third machine), but it's an improvement. And for a couple of days, everything ran very smoothly. However, apparently the forum has proven quite capable of hungrily devouring all new capacity; the faster things go, the more people show up, and the quicker we get back to where we were. You all collectively are basically Cookie Monster, but for servers. (Which is actually appropriate, if anyone's seen the very first thing the Muppet that became Cookie Monster came from; he was made for an IBM training film that Henson was hired to do, where he ate a computer. But I digress.) To stay with the amusement park analogy; the ride itself doesn't take long to go on, so we can move people through faster that way, but the capacity of the ride hasn't increased much so we still can only run a small number of people at a time. As such, we're probably going to increase the RAM of the machine later this week, so that I can increase the number of concurrent PHP sessions (i.e., the capacity of the ride). ...and now I have mental images of Muppets riding amusement part rides, and periodically eating them. Clearly, I need more coffee. (This post has been brought to you by the letter W and the number 16. Status Posts are a production of the Decaffeinated Sysadmin's Workshop.)
×