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

gitweb.cgi

From
HAH. Peter Anvin <hpa@zytor.com>
Date
Oct 18, 2005, 02:57 UTC
Message-ID
<43546492.3020401@zytor.com>

It is increasingly clear that gitweb.cgi is producing an unacceptable load on the kernel.org servers. Most of the hits we get are either the gitweb front page or the gitweb rss feeds, and it's eating I/O bandwidth like crazy.

This has become particularly painful during the current one-server outage.

Kay, gitweb really needs to be able to do caching, or be run behind a caching proxy. Otherwise I will have to turn it off until we can come up with a dedicated piece of server hardware for it.

	-hpa
Next: Kay Sievers
Message 1 of 15 in “gitweb.cgi”
  1. H. Peter AnvinOct 18, 2005
  2. Kay SieversOct 18, 2005
  3. H. Peter AnvinOct 18, 2005
  4. H. Peter AnvinOct 18, 2005
  5. Brian GerstOct 18, 2005
  6. Linus TorvaldsOct 19, 2005
  7. H. Peter AnvinOct 19, 2005
  8. Optimize common case of git-rev-list (was Re: gitweb.cgi)Linus Torvalds, Oct 19, 2005
  9. H. Peter AnvinOct 19, 2005
  10. Linus TorvaldsOct 19, 2005
  11. H. Peter AnvinOct 19, 2005
  12. Linus TorvaldsOct 19, 2005
  13. H. Peter AnvinOct 19, 2005
  14. Kay SieversOct 19, 2005
  15. Kay SieversOct 19, 2005

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.