Slashdot Mirror
Slashdot is Moving. Help Load Test!
We're moving the Slashdot cluster from Exodus East to Exodus West in the next couple days. In good Slashdot Tradition, we've opened up brak.slashdot.org for you to help load test the new cluster. Currently its almost an exact copy of our existing setup (missing a couple of webheads which will be up soon). The actual move will occur late at night (most likely tonight or tomorrow depending on how things go), and will hopefully involve only a few minutes of downtime as we copy the last of the data over the continent. Thanks for your help.
I checked out the brak./. and found old messages in my inbox. I'd prefer not to get deluged with old messages after the move occurs.
Just thought you should know in case you didn't know already (?).
What is music when you despise all sound?
Maybe you could read the first link on the right side of your screen labelled "FAQ". If you are sure that it has been asked my many others, it probably has, thus it is a "Frequently Asked Question". In case you can't find that link, try clicking here to find out what is powering /.
Come play Heroes of Might and Magic Mini online.
I live in LA, this is about twice as snappy as the current server is. time wget slashdot.org is about .9 ms slower than brak. Sux0rs to be east coast ;)
Photos.
Check out CmdrTaco's Journal for the answer. OSDN is consolidating servers.
Quick!! Get all your meta discussions in while there still is time!
Doesn't look hopeful:
to slashdot.org:
4 gige1-2.core1.Amsterdam1.Level3.net (213.244.165.101) 0 ms 0 ms 0 ms
5 CW-Level3.level3.net (213.244.165.246) 1 ms 1 ms 1 ms
6 bcr1-so-3-0-0.Amsterdam.cw.net (208.173.211.237) 1 ms 1 ms 1 ms
7 dcr2-loopback.NewYork.cw.net (206.24.194.100) 85 ms 85 ms 85 ms
8 cable-and-wireless-internal-isp.NewYork.cw.net (206.24.207.226) 85 ms 85 ms 85 ms
9 bbr01-g6-0.jrcy01.exodus.net (216.32.223.129) 85 ms 85 ms 85 ms
10 bbr01-p4-0.wlhm01.exodus.net (209.1.169.66) 90 ms 91 ms 91 ms
11 dcr04-g1-0.wlhm01.exodus.net (64.14.70.50) 91 ms 91 ms 91 ms
12 csr03-ve240.wlhm02.exodus.net (64.14.70.130) 150 ms 91 ms 91 ms
13 64.28.66.204 (64.28.66.204) 91 ms 91 ms 91 ms
to brak.slashdot.org:
4 gige6-0.core1.Amsterdam1.Level3.net (213.244.165.45) 0 ms 0 ms 0 ms
5 CW-Level3.level3.net (213.244.165.246) 1 ms 1 ms 1 ms
6 bcr1-so-3-0-0.Amsterdam.cw.net (208.173.211.237) 1 ms 1 ms 1 ms
7 dcr2-loopback.SantaClara.cw.net (208.172.146.100) 156 ms 156 ms 156 ms
8 ibr01-p4-0.sntc08.exodus.net (208.172.156.198) 156 ms 156 ms 156 ms
9 dcr02-g2-0.sntc08.exodus.net (66.35.194.4) 156 ms 156 ms 156 ms
10 csr02-ve242.sntc08.exodus.net (66.35.194.59) 157 ms 157 ms 157 ms
11 66.35.210.202 (66.35.210.202) 158 ms 158 ms 158 ms
Is this a reference to ?!?!?!?!
:)
Heh. Adult Swim. Next time are you going to name the server "Master Shake"?!?!?!?!
What kind of hardware does Slashdot run on?
I am on a fast pipe in Raleigh, NC and the elapsed load time went from .32s @ slashdot.org to .52s @ brak.slashdot.org. Not really a huge jump, but enough to notice on large page loads. The hops did drop from 20 to 18, fewer routers to break!
Kindness is the language which the deaf can hear and the blind can see. - Mark Twain
It appears worse for me in the midwest.
At work (dual T1s): ~45ms to the old one, ~80ms to the new one.
At Home (DSL): ~75ms old, ~150ms to the new one, twice as bad.
It doesn't help that I don't get to Cable & Wireless except by going to Chicago. Going east it was on the way, going west its just a needless round trip.
The new server is kinda having the crap beat out of it right now making ping comparisions a little irrelivant, however I find that generally traffic to and form Europe varies little based on geographic location. Basically, your signal is going to have to hop around europe till it hits a transcontential cable, then back around till it hits exodus. Most of the time taken will be in getting the signal to their network, where specifically in their network it has to go will make little difference.
From the Brak show, Brak is supposed to take care of Thunercleese's goldfish:
Thundercleese: Feed him exactly three milligrams of Tickle Snax! And be forewarned - three hams will certainly kill him. [close-up of Thundercleese's, uh, face] Three hams.
Brak:
[singing] Three hams will kill him,
Three hams will kill him,
I shouldn't feed him three hams! [Brak spreads his arms on the last word. Mr. Tickles hides behind the car.]
Thundercleese: Excellent! Your mission begins in the morning.
[Wipe to the room with Mr. Tickles's aquarium. Brak and Zorak are standing in front of it.]
Brak: Now what did Thundercleese say I was s'posed to feed Mr. Tickles for breakfast? I forget... [Thundercleese appears in a thought bubble by Brak's head. Brak turns to look at it.]
Thundercleese:
[singing] Three hams will fill him,
Three hams will thrill him,
Why don't you feed him three hams! [Thundercleese holds his arms up. A giant plate with three hams lands on his hands.]
Brak: Thank you, thought bubble! [The thought bubble disappears.]
Brak: Hey, Zorak, d'you think Mr. Tickles would like a delicious three ham omelet?
From my box @ surfnet.nl the "old" slashdot is 16 hops away and has avg. ping-times of 92ms. The "new" slashdot is 14 hops away and has avg. ping-times of 156ms. So its latency is over 50% higher (OMFG:D) but it's 2 possible points of failure closer:) Ofcourse this will totally depend on which network you're on as you can see from another reply.
0x or or snor perron?!
I've noticed latency issues with C&W in the last week at their peer/transit points. Has anybody else?
can you tell me what happened to Jon Katz?
Take a look at this article. A quote from the article:
Now, the one-time crusader for the geek underclass has decided to concentrate on writing more general technology articles and media commentary.
Never underestimate the power of fiber.
For some reason when I log onto the brak site, it says I have one new message but in fact there are no new messages! And for some reason, a tab for user number 178529 shows up in my account page in addition to my own information. All of this seems to have infested my account on the old server too. (This is real, I am not trying to make a lame joke.)
Could this be a newly identified issue with the server move?
And posting a comment (or logging in while previewing) times out. Previewing anonymously works, though.