[geeklog-devel] Article throttle.

[Justin Carlson]

I agree, sometimes they get a little link-happy and link it several
times ( including the index. ) It also falls apart when users go back
to the index from a linked article.
However, even if it only catches  50% of the users, that's a large
savings on bandwidth and the cpu(s) for that rush.

A more complex solution for watching the entire site can/has been
done, this one was just very simple.  In fact, a site-wide cache
system could be written, ( think about this for GL2 ) that creates
static pages and updates whenever content changes. This would of
course bloat the site, and should only be used by heavy traffic GL
users.  Just have to decide when/where to update the cached pages.
Thoughts?  Overkill? 




On Fri, 17 Dec 2004 23:17:56 +0100, Dirk Haun <dirk at haun-online.de> wrote:
> Justin,
> 
> >What this does is extremely simple. The owner of the website sets a
> >throttle, which is a number of guest users. Once this number is
> >reached, any article accessed from an external link or directly
> >accessed will display in print mode. This should greatly reduce the
> >number of database queries
> 
> Sounds interesting.
> 
> My suspicion, though, is that in most cases, it's the index page that is
> hit by most of the traffic. Especially Slashdot readers are known not to
> RTFA :P
> 
> Are our friends from Groklaw still around? Niels, Peter?
> 
> bye, Dirk
> 
> --
> http://www.haun-online.de/
> http://www.tinyweb.de/
> 
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://lists.geeklog.net/listinfo/geeklog-devel
>