Slashdot Mirror


Addendum to The Slashdot Effect Internet Paper

Spock_NPA writes "An addendum to the Slashdot Effect Internet Paper is available here. It details the effect of Slashdot on the Slashdot Effect Internet Paper."

35 of 101 comments (clear)

  1. That dang Slsahdot effect... by Oscarfish · · Score: 2
    ...will take down a server fast than NT can :)

    Seriously, the white paper and the addendum are interesting looks into many abject statistics...bundled up and analyzed to make sense against the fact that "[insert Slashdot featured server name here]'s connection is crap" or that their machines can't handle the load. I shouldn't complain, my sites are run on a shared server that wouldn't dream of handling Slashdot-caliber traffic just for a single hosting client.

    Interesting white paper, I enjoyed reading it.

    --

    --------

    Oscarfish.com: tropical fish with attitude. Way t

  2. Just how many people make up the Slashdot effect ? by maroberts · · Score: 2

    I'd love to know the answers to the following:

    How many registered people are there on Slashdot ?

    How many unregisterered people use Slashdot ?

    Maybe Slashdot ought to have a statistics page, showing the effect of the Slashdot effect on Slashdot!

    --

    Donte Alistair Anderson Roberts - hi son!
    Karma: Chameleon

  3. What about the other side? by JanneM · · Score: 3

    Isn't it time for the slashdot crew to write a statistical analysis of the reading frequency of the slashdot stories about the slashdot effect papers? If everybody keeps this up, we'll have a new academic subdiscipline in no time! "slashdot science", maybe, or "statistical geekology". If we get the terms 'postmodern' or 'cultural imperialism' into the title as well, we'll be rolling in grant money...

    --
    Trust the Computer. The Computer is your friend.
    1. Re:What about the other side? by zantispam · · Score: 2

      And the number of credits you start out with will be proportional to your Slashdot karma...

      Jedi Hacker (Apprentice) and Code Poet

      --

      censorship is a form of noise, which actively seeks to drown out content with silence - Crash Culligan
  4. addendum to the addendum? by seyed · · Score: 2
    will there now be an addendum to the addendum?

    "The Slashdot Effect as documented on the addendum documenting the Slashdot Effect on the original article on the Slashdot Effect."

    Some
    people
    have
    too
    much
    time
    on
    their
    hands.

    --
    "Everybody's Got Something to Hide Except for me and my monkey" - The Beatles "If you're not part of the solution, you'
  5. Slashdot Top Ten by ghoti · · Score: 3

    What about including a click-through counter in every link that's posted on ./? And then have a top ten ranking which links got clicked most in the last month or so (or maybe ranked by clicks/time unit).

    That would also be interesting to get an idea what load these servers have to deal with. I am not sure if the Slashdot Effect paper is really very representative.

    --
    EagerEyes.org: Visualization and Visual Communication
  6. Re:First post epidemic (offtopic) by Glenn+R-P · · Score: 2

    Yesterday's Red Hat article doesn't seem to have any first posts. It was released in the middle of the night after the kids had been sent to bed.

  7. Re:Recursion by JordanH · · Score: 2
    • When is the addendum to the addendum to the Slashdot Effect Internet Paper detailing the effect of Slashdot on the Slashdot Effect Internet Paper addendum due?

    Well we can't say when, but the addendum does address the question:

    • To conclude, this will be the last paper related to the Slashdot effect. If for some reason this addendum to the /. effect generates a new /. effect on the server, this will most likely not be presented as an Addendum to an Addendum.

  8. From the article by Money__ · · Score: 3
    On Jan 28th, around 1pm, Linux Today announced the article and published a text only version on their web site. Slashdot followed with an announcement of the article and a hyper link to the article at around 4pm. One can see the very impressive surge in hits after the Slashdot announcement in which the hit rate went from about 30 hits/minute up to over 250 hits/minute in about a 15 minute period.

    250 hits per minute. Now we know how big the slashdot effect is. Has anyone else seen surges this big (from 30/min to 250/min) from other sources other that /.?

    1. Re:From the article by Anonymous Coward · · Score: 2

      Whilst about an 800% increase in traffic is significant (30-250 hpm), 250 hits per minute is only just over 4 hits per second- hardly a major burden on Apache even on a modest Pentium 166.

      Yet many of the stories we heard about the "Slashdot Effect" prior to this paper (and its addendum) spoke of servers being brought to their knees by the increased traffic- not something that seems likely at a meagre 4 hps.

      This suggests that the paper only measured the magnitude of the effect for moderately popular articles- to gauge a 'Slashdottings' full potential for wreaking havoc, it would be useful to see the figures for truly popular articles (something like the annoucement of the original Mindcraft benchmarks, perhaps). My guess is that if the article is sufficiently interesting to pull in even 50% of the slashdot readership, the hit rate will go way over 4 hps.


      jtjm - (anon. coward only while waiting for his password to arrive. Suspects it's stuck in a mailqueue somewhere between slashdot and his ISP.)

    2. Re:From the article by gpoul · · Score: 2

      The question which has to be answered is, if these statistics are including or excluding graphics. If you have graphics on your html page you'll have much more hpms as you would have otherwise. If you have 5 .gif files on your page you'll have 4hpm * 6 = 24hpms. This is much more significant for P-166.

      Normally processor power isn't a real issue if you have no perl scripts or other dynamic content. (perl needs about 12 seconds to load on my i486)

      Bandwidth is much more critical at most server locations. (Yes, I know there are fibers out there ;-))) )

    3. Re:From the article by Inoshiro · · Score: 2

      I did some Apache load testing on my server. It doesn't have the bandwidth to handle heavy traffic.

      It's a Pentium 225 w/ 128mb of ram (it was 200Mhz, with only 96mb of ram when I benched). On static and SSI pages, it would certainly flood the pipe (512 simultanious requests, total of 8192 or so in Ab). On phtml (PHP3 page), the load went up to 65 for a while (heheh) ;-) Took 16 minutes to do the same load dynamic, that took 6 seconds static.

      Lesson to be learned: if you have dynamic content, have an Apache module to regenerate dynamic page X every N minutes. Serve up said generated page. This is what Slashdot does (IIRC), as well as other "serious" dynamic content sites (Yahoo patent comes to mind). I'm not sure if said module exists, but it'd be great if it did exist (instead of using cron scripts).
      ---

      --
      --
      Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
  9. Finding the referring site by navindra · · Score: 3

    There is a second resurgence, on a much smaller scale, two day's later which peaks at about 9:30am, with an abrupt fall off and then a re-resurgence around 6pm that day. This is seen in Figure 4. plot. The author scanned the various Linux news web pages for posting of the /. effect article but found none. This small resurgence occurring 2 days after the initial posting by /. is unexplained and open to interpretation.

    It's easy to log the referrer in Apache. I do it using a combination of .htaccess/cgi hacks. I've found some interesting things this way, including links from news sites/mailing-lists/newsgroups from over the world that I wouldn't have found otherwise. A link to the author's paper could have been posted on a russian linux news site, for example.

    If you're curious as to how this can be done under Apache, here's a rough description (apologies in advance for any ugly or careless code and any "Slashdot munging" in indentation, etc that may occur).

    (1) Point people to a CGI script, not the direct page. If you want this file to end with .html, this isn't a problem as you can have a .htaccess file that specifies something like "AddHandler cgi-script .html" or you can point people to the directory and respecify the DirectoryIndex.

    (2) Now here's the fun part. The script dumps the page to the requester then logs the interesting environment variables set by Apache.

    Example script:


    #!/usr/bin/perl
    # Navindra Umanee <navindra@cs.mcgill.ca>

    # Give them the page.

    open(indexPage, "/path/to/real/content.html");
    @fileStats = stat(indexPage);
    $modifiedTime = gmtime($fileStats[9]);
    $modifiedTime =~ s/^(...) (...) (\d\d?) (\d\d:\d\d:\d\d) (\d\d\d\d)/$1\, $3 $2 $5 $4 GMT/;

    # first, print HTTP header
    print "Content-Type: text/html\n";
    print "Last-Modified: $modifiedTime\n";
    print "Content-Length: $fileStats[7]\n";
    print "Accept-Ranges: bytes\n\n";

    # then, print body
    while(){
    ;print;
    }

    close(indexPage);

    # Now log the information.

    $log="../khtmltest.log";
    $localtime = `date`;

    open(logFile, ">>$log");
    print logFile "$localtime";
    print logFile "$ENV{'REMOTE_ADDR'} - $ENV{'REMOTE_HOST'}\n";
    print logFile "$ENV{'HTTP_USER_AGENT'}\n";
    print logFile "$ENV{'HTTP_REFERER'}\n";
    print logFile "\n";
    close(logFile);


    Cheers,
    Navin.

    1. Re:Finding the referring site by Jonas+�berg · · Score: 3
      Or; you can just change the logformat in Apache. This is what I use. It gives the same output format as the default log format, but has two entries appended to it for referer and user-agent.

      LogFormat "%h %l %u %t \"%r\" %s %b \"%{Referer}i\" \"%{User-agent}i\""

  10. I'm sure I've seen that before by xQx · · Score: 3

    I'm not sure if I'm babbeling sh*t here or not, but I am ABSOLUTLY SURE I have seen that paper before, reported on /. 6 or 12 months ago. It *MAY* have been the origional but I am fairly certain it was an addendum to the origional reporting the effects of the /. effect on the report of the /. effect.

    The graphs had lines saying when it was posted on betanews, /. etc... I dunno. Comments included "what next, a report on the /. effect on the report of the report of the report of the /. effect" etc.

    Again, I may just be dribbling sh*t (or dajavu or something)

    anyway.

    Cyas

    1. Re:I'm sure I've seen that before by NettRom · · Score: 2
      I'm not sure if I'm babbeling sh*t here or not, but I am ABSOLUTLY SURE I have seen that paper before, reported on /. 6 or 12 months ago. It *MAY* have been the origional but I am fairly certain it was an addendum to the origional reporting the effects of the /. effect on the report of the /. effect.
      I'll do a "Me too" to that. When I saw it I immediately remember that I had seen it before here on /. not the paper itself, but the addendum.

      It's quite interesting that a paper that has a Last Modified header saying "Tuesday, February 16, 1999" suddenly appears on /. as "news". That's slightly scary.

    2. Re:I'm sure I've seen that before by Bradley · · Score: 2

      I'll do a "Me too" to that.

      And I'll do a "me too" to the "me too".

      I checked, and Slashdot search turns up this as part of some quickies.

    3. Re:I'm sure I've seen that before by luge · · Score: 2

      Here, here. I guess it is sort of hard for them to search quickies, but if all of us remember this as already having been posted, certainly it can't be too hard for someone to do a check. And maybe the idea of a limit on the age of articles isn't too bad either...
      ~luge

      --

      IAAL,BIANLY

    4. Re:I'm sure I've seen that before by jacobm · · Score: 3

      Y'know, it would go a long way if they just kept a database of all the (non-"mailto:") links they posted and searched it when they posted a new story. They seem to have an automatic link-leeching thing going on anyhow, so they could probably do it totally transparently. All they'd need is another table in a database and a little routine that checked to see, when a story was about to be published, if the link was in the database- if so, have a little warning screen. "A link in your story ($linkName) has been previously posted on $oldLinkDate attached to the story $oldStoryName. Are you sure you want to post it again? [Yes] [No]"

      Might be worth coding up, /. people. Of course, there is the whole "time to write + performance hit / embarassment avoided" ratio, which might not be low enough to warrant implementation.

      --
      -jacob
    5. Re:I'm sure I've seen that before by Bradley · · Score: 2

      certainly it can't be too hard for someone to do a check

      Actually, I'd disagree with that. If it hadn't been a slashdot-related article, I wouldn't have been sure whether I saw it on slashdot, LWN, or somewhere else.

      When I've submitted stories, time differences mean that its generally just before the slashdot crew start going through their submissions in the morning. There are about 300-350 submissions, of which 5-10 are accepted. Noone can keep up with that, especially a story from February. Someone else might have posted that one, and, as part of quickies, it wouldn't have been as noticeable.

  11. eek by navindra · · Score: 2

    Ah suck, Slashdot did munge the stuff very slightly despite my best efforts and I managed to press "submit" instead of "preview" before fixing some of the code and removing that extraneous ';' before one of the print statements there.

    Oh well, if you have trouble figuring it out, you can always email me and ask.

  12. Re:Here are /. stats by Money__ · · Score: 3
    date: 6:21am

    uptime: 50 days, 21:18, 1 user,

    load average: 0.49, 0.35, 0.24

    processes: 132

    yesterday: 76525

    today: 1

    ever: 203679322

    These stats are shown in a 'slashbox' for registered users. A Custom Page that show these stats along with many other items.

    What's missing from the /. stats is the average ratio between 'proccesses' and 'unique visits'. This number would prove valuable. Rob? are you reading this ? :)

  13. Re:This will get funded! :) by Money__ · · Score: 2
    Dear over-stuffed officious suit at DOD,

    My name is Dr. Vinnyboombas and I seek funding for the following research:

    Building a quantitative model of Postmodern Slashdot Societies effect on Cultural Imperialism and Statistical Geekology. and ummm oh yea..can I have a supercolider and a mindstorm kit?

    Thank you Santa, I've been a good boy this year. :)

  14. This has not been slashdotted. by Ice+Station+Zebra · · Score: 2

    Even geeks sleep in on Sunday.

  15. Secondary surge explained by hta · · Score: 2

    The two-days-later surge would have been easily explained if he had looked at a referer log.

    It's the time when the story hits the top of the "older stories" list.

    Harald, counter.li.org slashdot victim/beneficary

    1. Re:Secondary surge explained by Bartmoss · · Score: 2

      Also don't forget that many, many sites carry/mirror freshmeat articles (courtesy of Daily Update and similar scripts), so there's another reason for "delayed" hits, and for a higher "background noise".

  16. Re:First post epidemic (offtopic) by Anonymous Coward · · Score: 2

    But look at it another way:

    A moderator, who has only five points to begin with, moderates your post to -1, using one of his points.

    Because of _you_, another more deserving post doesn't get moderated up.

    So even if it seems like it doesn't hurt someone...

    it does.

  17. Re:/. effect ==packet loss by Money__ · · Score: 2
    I agree with: 250 hits per minute is only just over 4 hits per second- hardly a major burden on Apache even on a modest Pentium 166.

    I would also posture a guess that at least 25% of the people experiencing the /. effect are indeed experiencing normal lag (packets dropped by routers a few hops away) combined with bad timing.

    For example: Prime time (United state 7PM to 10PM) evening net use is 'spotty at best'.

  18. Re:Something weird about these stats. by jacobm · · Score: 2

    The "today" stat is broken. It always says 1.

    --
    -jacob
  19. Re:Something weird about these stats. by jacobm · · Score: 2

    That would imply, though, that /. gets ~ 1 hit/minute, which isn't very plausible. I've actually never seen that counter be anything other than 1.

    On the other hand- as I've been checking, the "yesterday" figure keeps increasing. Probably the slashbox is just broken so that yesterday is today's stat and today points off into never never land somewhere.

    --
    -jacob
  20. Re:fr!st pS0t!!! by Black+Parrot · · Score: 3

    > actually i think all this "ph1r5t p05t" stuff is rather funny.

    A lot of stuff on /. is if you step back and look at it. There's also the meta-moderation that started after the moderation scheme was set up. And then there is the meta-meta-moderation comments that people started making after they noticed the meta-moderation. (It was amazing how quickly the term "meta-moderation" sprang up and came into common use.) Now I'm sure someone will point out that my commenting on meta-meta-moderation may qualify as meta-meta-meta-moderation; and of course you know what the comment on that will qualify for.

    Other things are the numerous "that's not worth posting" posts, which always strike me as really ironic, since someone is taking the trouble to comment on something that they say wasn't worth mentioning in the first place.

    And then there are the obligatory "that's been mentioned before" posts.

    And the "just got to work my political views in" posts, where people can't resist mentioning the moral status of [Bill_Clinton, George_Bush] (almost always in the subject line, since it doesn't do much good to hide inflammatory views down in the body of a post).

    I'm sure there are more that I haven't noticed. Perhaps this would be a suitable topic for a companion paper, or at least a Guide to Slashdot.

    All in all, I can imagine that this is really an entertaining site for those lurkers with a sense of humor about human nature.

    --
    It's October 6th. Where's W2K? Over the horizon again, eh?

    --
    Sheesh, evil *and* a jerk. -- Jade
  21. Re:Something weird about these stats. by zantispam · · Score: 2

    Actually, I seem to recall seeing the counter be greater than 1. Before Rob got the new servers, there were days that it would be 2, 3, 4, or even 5. I never saw it larger than 5, though.

    I had always assumed it to be current users (or current instances of root). This conclusion came from the fact that the more other people posted (Hemos, Cliff, Robin, et al), the higher the number was...

    'Course, I too, could be full of it...


    Jedi Hacker (Apprentice) and Code Poet

    --

    censorship is a form of noise, which actively seeks to drown out content with silence - Crash Culligan
  22. Re:addendum to the .sig addendum? by DoomHaven · · Score: 2

    I am such a geek that I found so FUNNY! Nothing like a bit a chemistry humor on a Sunday afternoon to brighten my day...

    Teacher: "Is the bond covalent or ionic?"
    Student1: "Isn't it ionic?"
    Student2: "Don't you think?"

    --
    "Don't mind me cutting myself on Occam's Razor"
  23. Money from /. effect. by ppanon · · Score: 2

    It occurred to me that ad banner companies could make a bit of extra cash from the slashdot effect. Suppose you were an ad company with banners at many different sites, if you kept track of which sites were referenced on /., you could sell advertising on those sites at a premium during the /. effect. It would be like buying a spot during the Super Bowl. You're guaranteed to have a whole bunch of eyes look at your ad.

    Of course it probably won't work too well if you're trying to advertise MS Windows 2000 :-)

    --
    Laissez lire, et laissez danser; ces deux amusements ne feront jamais de mal au monde. - Voltaire
  24. Slashdot Statistics by kcarnold · · Score: 2

    I propose that we launch a massive Slashdot statistics program. It would involve a significant amount of invasion of "privacy", i.e., almost every link off of /. would be logged, but we could get a lot of raw data to look at in interesting ways. Here are a few of my ideas:

    • Karma tracking: This itself would not need any data-gathering things. Grab stats based on user's karmas. Examples:
      • Number of requests to main page by karma
      • Number of comments posted per (unit of time) vs. karma
      • Average moderation vs. karma
      • Number of users at a certain karma
      • Number of comments containing the words "FIRST POST!!!" vs. karma
      • Collary to the last one: Number of times it actaully is first post vs. karma
    • Stats:
      • How many times users check their stats (could also study karma on this).
      • Number of times other users check a user's stats
    • Areas: Record popularity of different areas of Slashdot (Funny, Red Hat, GNU, etc.) by how many users read articles and of those, how many post comments, and the average moderation of those comments (and average karmas of people who post there; what "the elite" visit).
    • Referring=Slashdot: Quick redirects embedded in each link off of Slashdot (at least on the main page, maybe even on users' comments, and don't forget those *@$# ads) could could hits by link. This would make studying the Slashdot Effect even easier. If the Slashdot servers were fast enough, and you could analyze the ethical issues of doing so, links could link to a cgi script that would request the web page, and this way the banner ads and other stuff would be preserved, but you could do more counts like whether the server was overloaded or (ethical question mark) track links from the linked-to site.

    There are more! Let someone else suggest them, though. I think that analyzing the raw data gained by these approaches would be a good statistics project for any upper high school or college student. And hey, I like Slashdot, and if I get credit for it, even better! (Well, it would be mostly raw data, not the real site, but still...)

    Ken

    PS - I would do such a project. Anybody who wouldn't?