Slashdot Mirror

← Back to Stories (view on slashdot.org)

Slashdot is Moving. Help Load Test!

Posted by CmdrTaco on from the please-wear-a-hardhat dept.

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.

6 of 344 comments (clear)

  1. FYI reupdate the message inbox of users by sielwolf · · Score: 5, Informative

    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?
  2. Re:nows a good time to explain..... by ajakk · · Score: 5, Informative

    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.
  3. Re:Why is it moving? (nc) by Louis_Wu · · Score: 5, Informative

    Check out CmdrTaco's Journal for the answer. OSDN is consolidating servers.

  4. Re:Serious question by Anonymous Coward · · Score: 5, Informative

    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

  5. Re:nows a good time to explain..... by the_danielsan · · Score: 5, Informative

    What kind of hardware does Slashdot run on?

  6. I imagine it won't make much difference by Sycraft-fu · · Score: 5, Informative

    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.