From: "J.H." <warthog19@eaglescrag.net>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: Petr Baudis <pasky@suse.cz>, Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Support caching projects list
Date: Thu, 13 Mar 2008 17:30:01 -0700 [thread overview]
Message-ID: <1205454601.2758.10.camel@localhost.localdomain> (raw)
In-Reply-To: <76718490803131727p451967hee96ff26206c97b7@mail.gmail.com>
You would be better off using some of the logic I've got in the caching
version of gitweb to prevent the race condition.
- John 'Warthog9' Hawley
On Thu, 2008-03-13 at 20:27 -0400, Jay Soffian wrote:
> On Thu, Mar 13, 2008 at 8:22 PM, Petr Baudis <pasky@suse.cz> wrote:
>
> > There is a more conceptual problem though - in case of such big sites,
> > it really makes more sense to explicitly regenerate the cache
> > periodically instead of making random clients to have to wait it out.
>
> Fork off a child to update the cache?
>
> > Unlikely. Currently the machine is mostly IO-bound and only small
> > portion of CPU usage comes from gitweb itself.
>
> Except that if it were FastCGI or mod_perl you could just keep the cache in
> memory.
>
> j.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-03-14 0:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 23:14 [PATCH] gitweb: Support caching projects list Petr Baudis
2008-03-14 0:07 ` Jay Soffian
2008-03-14 0:22 ` Petr Baudis
2008-03-14 0:27 ` Jay Soffian
2008-03-14 0:30 ` J.H. [this message]
2008-03-14 12:17 ` Jakub Narebski
2008-03-14 0:36 ` J.H.
2008-03-17 17:49 ` repo.or.cz renovation Petr Baudis
2008-03-17 18:11 ` Petr Baudis
2008-03-17 18:44 ` J.H.
2008-03-17 20:41 ` Jakub Narebski
2008-03-17 21:09 ` Jakub Narebski
2008-03-14 15:29 ` [PATCH] gitweb: Support caching projects list Jakub Narebski
2008-03-14 21:11 ` Jay Soffian
2008-03-14 0:19 ` Junio C Hamano
2008-03-14 8:35 ` Frank Lichtenheld
2008-03-14 12:14 ` Jakub Narebski
2008-03-17 17:40 ` Petr Baudis
2008-03-15 21:44 ` Jakub Narebski
2008-03-16 0:56 ` Miklos Vajna
2008-03-16 11:41 ` Frank Lichtenheld
2008-03-16 16:52 ` J.H.
2008-03-16 18:37 ` Jakub Narebski
2008-03-16 22:37 ` J.H.
2008-03-16 23:39 ` Jakub Narebski
2008-03-17 18:10 ` repo.or.cz renovated Petr Baudis
2008-03-17 19:09 ` Junio C Hamano
2008-03-17 19:25 ` Petr Baudis
2008-03-17 19:34 ` Theodore Tso
2008-03-17 19:54 ` Petr Baudis
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=1205454601.2758.10.camel@localhost.localdomain \
--to=warthog19@eaglescrag.net \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
--cc=junkio@cox.net \
--cc=pasky@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).