git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Gitweb caching: Google Summer of Code project

From
LWLea Wiemann <lewiemann@gmail.com>
Date
May 30, 2008, 14:59 UTC
Message-ID
<4840166C.3030903@gmail.com>
In-Reply-To
<200805301202.25368.jnareb@gmail.com>
Jakub Narebski wrote:
> even if you don't implement two caching API's at least make it
> possible to easy change caching backend.
Sure, I'll keep that in mind.
> Note also that memcached may not have sense for single machine [...],
>  and does not make sense for memory starved machines...

For single machines, memcached certainly works fine. For on memory-starved machines with HD caches, you'd have to cache the aggregate HTML data, not the data in the backend. So as long as I'm working on the backend (repository) cache, memcached should be fine.

> IIRC the policy usually is that one can install packages
> from main (base) repository for Linux distribution used on server,
libcache-memcached-perl is in Debian stable; that's fair enough I think. 
  Cache::Memcached::Fast doesn't seem to be in Debian as of now, but I 
wouldn't worry about performance unless it comes up.
>>> By the way what do you think about adding (as an option) information
>>> about gitweb performance to the [HTML] output,
> 
> I'd try to add it when I'd have a bot more of free time
I'd probably wait with this until I've written the Perl Git API.
-- Lea
Previous: Jakub NarebskiNext: Petr Baudis
Message 9 of 18 in “Gitweb caching: Google Summer of Code project”
  1. Lea WiemannMay 27, 2008
  2. Jakub NarebskiMay 27, 2008
  3. Lea WiemannMay 27, 2008
  4. Jakub NarebskiMay 28, 2008
  5. Lea WiemannMay 28, 2008
  6. Jakub NarebskiMay 29, 2008
  7. Lea WiemannMay 30, 2008
  8. Jakub NarebskiMay 30, 2008
  9. Lea WiemannMay 30, 2008
  10. Petr BaudisMay 30, 2008
  11. Lea WiemannMay 30, 2008
  12. Petr BaudisMay 30, 2008
  13. Rafael Garcia-SuarezMay 30, 2008
  14. J.H.May 30, 2008
  15. Junio C HamanoMay 30, 2008
  16. Lea WiemannMay 30, 2008
  17. Lea WiemannMay 30, 2008
  18. Jakub NarebskiMay 31, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.