Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

Re: Renovating Best Nodes

by halley (Prior)
on Feb 13, 2004 at 15:27 UTC ( #328796=note: print w/ replies, xml ) Need Help??


in reply to Renovating Best Nodes

There doesn't appear to be a 'Selected Best' nodelet. I'd suggest 10~12 instead of 50, but I miss the 'all time best' nodelet already. For the links I used often, I'll just add those to my 'Personal Nodelet' instead.

--
[ e d @ h a l l e y . c c ]


Comment on Re: Renovating Best Nodes
Re: Re: Renovating Best Nodes
by demerphq (Chancellor) on Feb 13, 2004 at 15:58 UTC

    Yep. I was planning to wait on that one until the number of nodes could be user controlled.

    Sorry about All-Time Best, but hopefully it will be for the best in the end. :-)


    ---
    demerphq

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


      I see two issues: (1) user arguments to control a widget is not well-established here, so you're "waiting" for a lot to be implemented; and (2) wouldn't user-controlled best counts be harder on the server? At minimum, you'd have to calculate the maximum "selected" nodes for a given refresh time, then save multiple versions of nodelet content.

      --
      [ e d @ h a l l e y . c c ]

      I'm pretty sure you'll not get user preferences in the nodelets for quite a while (if ever). Nodelets are rendered on every page load and so are best when they can be cached. And cached nodelets can't be user-specific.

      Your caching for best/worst nodes is quite nice but it still reads quite a few records out of the database. Doing that 4 times for every page load would probably end up with more DB load than we had before your work.

      - tye        

        I'm pretty sure you'll not get user preferences in the nodelets for quite a while (if ever). Nodelets are rendered on every page load and so are best when they can be cached. And cached nodelets can't be user-specific.

        Yep. When i wrote that reply I hadn't realized the implications of the node caching on what I was saying. In fact I _keep_ forgetting them.

        Your caching for best/worst nodes is quite nice but it still reads quite a few records out of the database. Doing that 4 times for every page load would probably end up with more DB load than we had before your work.

        I agree totally. Would it be too much (in terms of policy etc) to make small versions of the various nodelets? With say 5 lines in each, and a link to their respective full page version?


        ---
        demerphq

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


Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://328796]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (14)
As of 2015-07-06 18:42 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (80 votes), past polls