public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Planet Gentoo released
Date: Fri, 11 Mar 2005 03:39:25 -0800	[thread overview]
Message-ID: <20050311113925.GB25986@curie-int.orbis-terrarum.net> (raw)
In-Reply-To: <42317293.3040900@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]

On Fri, Mar 11, 2005 at 10:27:31AM +0000, Daniel Drake wrote:
> Donnie Berkholz wrote:
> >So I can see my blog entries show up on it without waiting around for
> >half of forever. More than 15 minutes is very annoying.
> >
> >What's the rationale for having it happen less often? Maybe it's a major
> >drain on resources, but from my ignorant mind, it seems unlikely.
> >
> >Has anyone checked with some other planet maintainers (e.g.,
> >planet.freedesktop.org, planet.gnome.org) to see how often they do it?
> It is currently set to update every hour (xx:02). I personally think this 
> is a good enough delay, to avoid too much pointless traffic etc.
> 
> On the other hand, I was also wondering how regularly other planets update. 
> If anybody knows anyone in the know, please get me in contact.
> 
> How often is Planet Gentoo Experimental updating?
From my Apache logs, it seems to be once an hour, around xx:31.

I agree that once an hour is a very reasonable time, as Planet/0.2
fetches the page every time according to my logs, but I'm not certain if
this is because of the way I build my RSS feed.

I don't know if Planet includes 'If-Modified-Since' in it's requests.
If it does, then I think halving the time may be appropriate, as nearly
all requests will return only an HTTP header as the page has not
changed. The traffic and load in this case should be very small.

-- 
Robin Hugh Johnson
E-Mail     : robbat2@orbis-terrarum.net
Home Page  : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ#       : 30269588 or 41961639
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 241 bytes --]

  reply	other threads:[~2005-03-11 11:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10 15:33 [gentoo-dev] Planet Gentoo released Daniel Drake
2005-03-10 16:26 ` LostSon
2005-03-10 16:37   ` Chris Gianelloni
2005-03-10 16:38   ` Daniel Drake
2005-03-10 16:43 ` Thomas de Grenier de Latour
2005-03-10 16:48   ` Peter Johanson
2005-03-10 19:48 ` Donnie Berkholz
2005-03-10 20:14   ` Lance Albertson
2005-03-11  3:28     ` Donnie Berkholz
2005-03-11  3:56       ` A. Khattri
2005-03-11  5:58         ` Donnie Berkholz
2005-03-11  9:51           ` Michael Cummings
2005-03-11  9:51             ` Michael Cummings
2005-03-11 19:55             ` Donnie Berkholz
2005-03-11 20:38               ` Mike Frysinger
2005-03-12  3:56                 ` Aron Griffis
2005-03-11 20:42               ` Hasan Khalil
2005-03-11  3:57       ` Hasan Khalil
2005-03-11 10:27       ` Daniel Drake
2005-03-11 11:39         ` Robin H. Johnson [this message]
2005-03-11 12:19           ` Daniel Drake
2005-03-11 17:07         ` Rob Cakebread
2005-03-11 13:13   ` Ciaran McCreesh
2005-03-11  0:18 ` marduk
2005-03-12 17:17 ` Wolfram Schlich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050311113925.GB25986@curie-int.orbis-terrarum.net \
    --to=robbat2@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox