I am receiving reports from a couple of different sources about issues with LGpedia load times. I am unable to reproduce the issue myself (even image-heavy pages are loading within 3 seconds or so for me), and need help tracking down the issue. If you're experiencing problems with LGpedia, are you also experiencing problems with the rest of the site? Who is your ISP? Can you email me a traceroute (or tracert, depending on OS) to lgpedia.nitemarecafe.com while the issue is occuring for you? (wintermute AT nitemarecafe DOT com) This should help me track it down some, and rule out a saturated link or some-such.
Thursday, September 4, 2014
LGpedia Issues
I am receiving reports from a couple of different sources about issues with LGpedia load times. I am unable to reproduce the issue myself (even image-heavy pages are loading within 3 seconds or so for me), and need help tracking down the issue. If you're experiencing problems with LGpedia, are you also experiencing problems with the rest of the site? Who is your ISP? Can you email me a traceroute (or tracert, depending on OS) to lgpedia.nitemarecafe.com while the issue is occuring for you? (wintermute AT nitemarecafe DOT com) This should help me track it down some, and rule out a saturated link or some-such.
Subscribe to:
Post Comments (Atom)
Ummm…you fixed it? lol. I was getting ready to do a traceroute, clicked on the lgpedia link so that I'd have the whole URL to paste in, and…the site came up in a couple of seconds, just like normal! Searched for several things…Bree, Daniel, cassieiswatching…everything seems to be normal now. NOTE: previously, during its super-slow phase, when I'd type something in the search, I wouldn't get any "suggestions"…though maybe I *would* have if I had waited a few minutes.
ReplyDeleteDid you change something, or did it "heal" itself?
I did nothing to fix it, so, this is kind of strange. I *did* enable multi-site on the blog, and entered a wildcard DNS entry for *.nitemarecafe.com, which MAY have had some impact, but the blog is still multi-site (I did upgrade to 4.0, though) and lgpedia has it's own DNS entry. The only thing I can think is that the multi-site stuff in Wordpress interfered somehow, and the upgrade to 4.0 fixed it. Let me know if it happens again, and I'll maybe disable multi-site and see if that helps. Strange that I could never re-create the issue, though.
ReplyDeleteHmmm. Since I don't know the time/dates of that series of events, maybe this information will help:
ReplyDeletelast night (Saturday night) after modelmotion got on SL, around midnight CST (so technically it had just become Sunday AM in my time zone) I tested lgpedia out again, and it was still super-slow. So, what ever fixed it happened AFTER that time. Maybe Cassie knew we needed it?
Hmmm... During that timeframe, nothing was changed. So, it must've been Cassie ;) If it happens again, let me know. It bothers me when things "fix themselves" and I have no idea what happened. lol
ReplyDeleteIt's still not fixed.
ReplyDeleteI can't reproduce the issue, so I'm not certain what it is... Does this site load fine, or is it slow as well? I'm going to try something with multi-site and see if it resolves the issue... It'll be changed by the time you read this, I'm sure :)
ReplyDeleteedit - And multi-site is off. Let me know if it still is not fixed. traceroutes to lgpedia.nitemarecafe.com might be helpful, but only if this site is slow as well...
Well, I didn't try it again (since Sept 8 early AM) until just now, but…
ReplyDelete1. For me, lgpedia is STILL running fast; faster than Cu Roi chasing down an ARG drop!
2. During that former period when lgpedia was taking minutes to load, THIS website (www.nitemarecafe.com) was still running normally.
That's my 2¢ worth of input.
Thanks for your input, ahcapella. It may have been the multi-site thing I was talking about. Will have to wait for Ryan to verify whether it's still slow for him or not.
ReplyDeleteHoly Cassie on a cracker! 25 hours later, tried it again for grins, assuming all would be right in the world. Nope. Lgpedia is back to being slow as molasses! (My immediate clue was that when I typed something into search, no "suggestions" appeared. I suspect that Ryan can back me up on that.) I have no idea how these things work, but…could it be on a server that has become unreliable? I don't get why it's gone from one extreme to the other, back & forth.
ReplyDeleteIf it were a server issue, the main site would be slow as well, and that doesn't appear to be the case. I'm going to re-enable multi-site, since disabling that didn't work. I supposed it *could* be the Google Analytics code, but that's been there for awhile *and* also runs on the main site, so that doesn't make much sense. But I think Analytics keeps track of things like page load times, so I'm off to check the stats there as well...
ReplyDeleteedit: I've disabled Analytics on LGpedia, in case that was causing any issues...
Still slow, I’m afraid. And consistent—taking ~2:30 to bring up the "cassieiswatching" entry. (Though, this time, the picture came up at the same time as the text. Maybe it's in a cache somewhere. A cache with Cassie's face in it…shudder!)
ReplyDeleteAnd...back to fast again. lgpedia loaded right away. "cassieiswatching" came up in a couple of seconds. I type "Bree," and instantly get multiple suggestions.
ReplyDeleteIt could definitely be a caching issue. LGpedia uses caching, and a new version of the caching software is out... Unfortunately, it's a shared server and I don't have control over that... Trying to figure out how to disable caching to see if that helps..
ReplyDeleteWell…it's nighttime, and lgpedia is still running fast. There goes my theory that the server is running on a solar panel. Haha!
ReplyDeleteLOL. As soon as I'm done with my work for the evening, I'll try to figure out how to kill the server-site caching to see if it helps :)
ReplyDeleteAnd... Mod Pagespeed has been disabled. Please let me know if the problem happens again going forward.
ReplyDeleteSmooth sailing so far, Captain!
ReplyDeleteThanks :) I really hope that did it. Only other option otherwise is to move it to a new server, which would have to be the one at home, then it becomes susceptible to cable outages, plus much less bandwidth. Not the best solution ;)
ReplyDelete