Normally I don't interject, because I really don't see the point of some changes suggested, but since you ask...

As it stands, the monastery has turned into a monolith - several hundred db queries per page I believe. That's crazy - whatever happened to KISS?

The site is already crawling on several (3 now, isn't it?) servers.

I would only say no problem if each article thread was cached, and the DB was only hit for each menu only once every couple of minutes. Here's a RL example. We have "live" news feeds that our client's can embed in their pages that are called through SSI. The feed article DB is updated hourly. Templates are designed by customers, and populated once an hour, creating static files. This way, each feed template builds a live page once an hour. When the SSI is called, if the populated template is less than 60 minutes old, it's served, else it's rebuilt from the DB. This results in each designed feed template resulting in one hit on the DB per hour. This way, we can safely offer the feature to all 1000 odd domains on the server without having to worry about the overhead. Now, I know Newest Nodes is different, but is each view generated on the fly, or shown from a cache? Would anyone *really* be bothered if these threaded indices were cached and only rebuilt once every 2-3 minutes? Just something to think about...

I can't believe that this much hardware is needed to serve a couple of hundred people at a time. Unfortunately, I don't think this can be fixed without a complete rethink of the underlying design philosophy.

demerphq. I can understand you wanting to improve the monastery. You are a great coder, but I get a gut feeling that the inmates are running the asylum (that's meant to be a ;-) not a :( - ok! :)

I would love to see you using your (seemingly unbounded :) energy towards making each page load twice as fast. I can't see why each page needs more than a dozen or so DB queries.

Or, to start with a clean slate and create a "PM lite", with pages that load a lot faster, with compromises made on customizations. I would use it, probably most of the time. In the same way that I read slashdot with images turned off.

Or maybe I'm just turning into a grumpy old man (well, I *am* nearly 34 :)

.02

cLive ;-)

In reply to Re: Does the monastery want a threaded newest nodes? by cLive ;-)
in thread Does the monastery want a threaded newest nodes? by demerphq

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.