why is metafilter so slow recently? January 6, 2002 2:31 PM   Subscribe

MetaFilter has been very slow all weekend - first time this has happened since I joined last September. Access has been fine. But when I try to jump to the comments - or post a comment - it keeps timing out. What's going to happen when Monday comes? Can the greedy Google bots be munching away at more than 33% or would this alone be enough?
Any way we users can lighten the load on our side?
posted by MiguelCardoso to Uptime at 2:31 PM (9 comments total)

Finally got through. Also the pages, when they download appear with the HMTL code("a href" etc)before either timing out or, if I'm lucky, finally loading...
posted by MiguelCardoso at 5:20 PM on January 6, 2002


Things are zippin' along fine for me. Of course, I'm in California (as opposed to Portugal), on a T1. Not bragging, mind you, just saying that the slowness that you're experiencing is most likely an issue local to you.
posted by Optamystic at 5:41 PM on January 6, 2002


Flying here too. Its probably a local ISP problemo.
posted by skallas at 5:50 PM on January 6, 2002


Whats your ping time to www.metafilter.com?

Me:
D:\>ping www.metafilter.com

Pinging metafilter.com [209.10.108.201] with 32 bytes of

Reply from 209.10.108.201: bytes=32 time=70ms TTL=113
Reply from 209.10.108.201: bytes=32 time=60ms TTL=113
Reply from 209.10.108.201: bytes=32 time=50ms TTL=113
Reply from 209.10.108.201: bytes=32 time=60ms TTL=113
posted by skallas at 5:51 PM on January 6, 2002


Pinging metafilter.com [209.10.108.201] with 32 bytes of data:

Reply from 209.10.108.201: bytes=32 time=369ms TTL=115
Reply from 209.10.108.201: bytes=32 time=356ms TTL=115
Reply from 209.10.108.201: bytes=32 time=356ms TTL=115
Reply from 209.10.108.201: bytes=32 time=368ms TTL=115


I've had some weirdness from Korea too, FWIW.
posted by stavrosthewonderchicken at 9:45 PM on January 6, 2002


ping metafilter.com

Pinging metafilter.com [209.10.108.201] with 32 bytes of data:

Reply from 209.10.108.201: bytes=32 time=25ms TTL=113
Reply from 209.10.108.201: bytes=32 time=63ms TTL=113
Reply from 209.10.108.201: bytes=32 time=57ms TTL=113
Reply from 209.10.108.201: bytes=32 time=43ms TTL=113

Ping statistics for 209.10.108.201:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 63ms, Average = 47ms

From RoadRunner NYC in Queens.
posted by riffola at 10:11 PM on January 6, 2002


Thanks Optamystic, skallas, stavrosthewonderchicken and riffola! Looks like it's my particular connection to MetaFilter - though everything else on the WWW, i.e. everything boring, is flying. Perhaps it's time for paranoia to set in, like this is the MeFi server's way of saying "slow down, pudner".

*Sound of a local provincial hick from faraway Portingale apologizing for the inconvenience, with pinging, plonking noise of euros falling on pinewood as he saves up for T1 connection(only got cable), extra RAM(only got 512K)and new floating Canadians-only iMac, since he's at it.*
posted by MiguelCardoso at 11:40 PM on January 6, 2002


The cnxn from the UK to some sites was slow this weekend. I had problems with MeFi and a bunch of others (nytimes, I remember). But, curiously, /. was OK.
posted by andrew cooke at 3:42 AM on January 7, 2002


But can you get on 13578, the cokehead-peeing-on-airline thread? That is what separates the hosts from the mere guests. All I get is the old blank stare.
posted by MiguelCardoso at 3:46 AM on January 7, 2002


« Older Previewing the Poster's Name   |   Reverse chronological display Newer »

You are not logged in, either login or create an account to post comments