Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?
 
PerlMonks  

Random Top Nodes

by demerphq (Chancellor)
on Feb 07, 2004 at 19:12 UTC ( [id://327347]=monkdiscuss: print w/replies, xml ) Need Help??

I was wondering what folks would think about Best Nodes having an extra section or two of randomly chosen top nodes? I wrote a patch that is currently awaiting application that lists "Random Nodes from the Top 1000 of All Time" and "Random Nodes from the Top 500 of Last 30 Days".

Would this be appreciated by the monks out there?

Personally I think that it would. At bare minimum it would get some of the contenders listed and maybe would farm out the votes to some of them so that best nodes was not so affected by vote inflation.

Feedback appreciated as I don't know if the gods think this is a good idea.


---
demerphq

    First they ignore you, then they laugh at you, then they fight you, then you win.
    -- Gandhi


Replies are listed 'Best First'.
Re: Random Top Nodes
by kvale (Monsignor) on Feb 07, 2004 at 19:46 UTC
    I think this is a great idea. Once I am done with Newest Nodes, I often cast about for other interesting nodes to look at. The top 500 or 1000 would be fine, but any node with a rep some specified number of standard deviations above the norm would probably be interesting to me.

    The XP redistribution doesn't matter so much to me, but can't hurt I suppose.

    -Mark

Re: Random Top Nodes
by arden (Curate) on Feb 07, 2004 at 19:49 UTC
    demerphq, I like the idea, in fact I think it's great. My only concern (not having seen the code) is how much of a hit will it put upon the server? We know that the Monastery can be slow at times as it stands now, how will it be if we're adding calls to randomly choose ten nodes from a list of 1,000 and another randomly chosen ten from a list of 500? I don't know. I'm just wondering if anyone else has thought about it.

    I do hope that it gets implemented, but I think we need to be ready to pull it quickly if the server degrades due to it.

    - - Arden.

      Personally i doubt if the hit will be much more than currently is encountered with Best Nodes. (And there is experimental evidence that suggests as much.) However actually determining the costs of this proposal is beyond my abilities at the time. One of the gods must make this decision.


      ---
      demerphq

        First they ignore you, then they laugh at you, then they fight you, then you win.
        -- Gandhi


Re: Random Top Nodes (nice)
by tye (Sage) on Feb 08, 2004 at 05:58 UTC

    I like the idea. It may be quite a bit more efficient to compute the XP cut-off nightly (when $NORM is computed and votes are handed out) so the DB can throw out nodes as it scans instead of having to sort them all in order to find the top 1000 (is MySQL smart enough to use a limited-size heap for such?). Yes, even the current non-random listings could probably benefit from such a change.

    Then there is the risk of people reloading the page over and over to get different samples and the DB load of such. Probably worth trying after I work out the current web server performance issues that caused me to roll back the DB performance stats gathering...

    Perhaps Best Nodes should only list best of year, best of month, best of week, and best of day while a separate node lists a random selection of all-time best nodes.

    - tye        

      ...while a separate node lists a random selection of all-time best nodes.

      I would be for that. And I think that could be done rather cheaply by just determining the top 1000 nodes of all time only once a day or so. If it were plain mod_perl, I would just store the id's of those 1000 in an array at a server start time (before forking) and randomly select from that from memory without ever touching the disk. It would only make startup a little longer, but would not affect runtime in general.

      Liz

Re: Random Top Nodes
by gmax (Abbot) on Feb 08, 2004 at 11:08 UTC

    I like the idea as a method to improve the visibility of those nodes that are currently in a dark zone, i.e. not in the Best Nodes, not in Tutorials, not in any special list, so people can't get to know about those gems unless they stumble into them by chance.

    I believe it's time to recognize that the Monastery needs a more mature tool to browse those interesting nodes.

    As for the method of enhancing the visibility of deserving nodes, I liked your previous suggestion better, just because I believe it is the fastest to implement. If I could choose the best method, though, I would endorse tilly's plan of having best-of-the-month/year lists, which seems to have also tye's approval.

    Go for it. Whichever method is chosen will improve the Monastery's mission of spreading knowledge.

     _  _ _  _  
    (_|| | |(_|><
     _|   
    

      Many have mentioned my earlier idea of modifying Super Search to include reputation as a search criteria. I looked into it but the supersearch code is pretty specialized stuff, and I have to admit that I was unable to identify an easy patch to it. I suspect that effectively modifying it will require tye's skills and understanding of how it works. Its definately not a simple job to my eyes.


      ---
      demerphq

        First they ignore you, then they laugh at you, then they fight you, then you win.
        -- Gandhi


Re: Random Top Nodes
by bassplayer (Monsignor) on Feb 08, 2004 at 06:56 UTC
    ++

    High Monk Reputation doesn't necessarily equate to Elevated Perl Skills, but High Node Reputation often does equate to Great Reading.

    bassplayer

Re: Random Top Nodes
by xenchu (Friar) on Feb 07, 2004 at 21:52 UTC

    I think it would be a good idea. I would prefer to see 'Random Nodes from the Top 1000 Nodes of All Time' but either would be interesting.

    xenchu


    The Needs of the World and my Talents run parallel to infinity.
Re: Random Top Nodes
by belg4mit (Prior) on Feb 07, 2004 at 19:59 UTC

      These approaches dont know about node reputation. So its not going to be the same thing at all. But you can still use them if my patch gets applied.


      ---
      demerphq

        First they ignore you, then they laugh at you, then they fight you, then you win.
        -- Gandhi


        >These approaches dont know about node reputation.

        My point exactly. Thusly avoiding the positive-feedback loop, as well as shining further light on nodes which may have initially gone unnoticed.

        --
        I'm not belgian but I play one on TV.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: monkdiscuss [id://327347]
Approved by Corion
Front-paged by calin
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (3)
As of 2024-04-25 19:55 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found