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

Re: [RFC/PATCH] gitweb: Paginate project list

From
LHLars Hjemli <hjemli@gmail.com>
Date
May 13, 2008, 19:30 UTC
Message-ID
<8c5c35580805131230p37953e33he97803c0609012fa@mail.gmail.com>
In-Reply-To
<200805131904.38317.jnareb@gmail.com>
On Tue, May 13, 2008 at 7:04 PM, Jakub Narebski <jnareb@gmail.com> wrote:
Show 15 quoted lines
> On Tue, 13 May 2008, Lars Hjemli wrote:
>  > On Tue, May 13, 2008 at 8:55 AM, Jakub Narebski <jnareb@gmail.com> wrote:
>  >>
> >> But please take into account that gitweb performance, and I guess any
>  >> git web interface performance, is I/O bound and not CPU bound (at least
>  >> according to what I remember from J.H. emails).  So a little more
>  >> processing is I think less important than avoiding hitting the repos.
>  >
>  > Yeah, that's a pretty convincing argument for "cache the data, not the
>  > output", at least for gitweb (cgit never touches the repos to generate
>  > the project list/search).
>
>  First, this is less argument for "cache data" against "cache output",
>  only against disregarding "cache data" for assumed performance reasons,
>  while it "cache data" can be useful in some places.
Ok, then I misinterpreted your argument.
>  Second, gitweb's projects list page contains "Last Changed" column,
>  and you _*have*_ to hit repositories for this data

No you don't. One alternative is to use the post-update hook in each repo to update a separate file with info about last-changed-time. Another (less accurate) alternative is to stat one or more of packed-refs and refs/heads/*; cgit uses both of these alternatives to avoid hitting the repo (i.e. object-db) when the project list/search page is generated.

-- larsh

Previous: Kristian HøgsbergNext: Jakub Narebski
Message 18 of 20 in “gitweb: Simplify git_project_list_body”
  1. gitweb: Simplify git_project_list_bodyJakub Narebski, May 1, 2008
  2. gitweb: Allow project description in project_index fileJakub Narebski, May 2, 2008
  3. Miklos VajnaMay 2, 2008
  4. gitweb: Allow project description in project_index fileJakub Narebski, May 3, 2008
  5. Miklos VajnaMay 4, 2008
  6. gitweb: Project searchJakub Narebski, May 9, 2008
  7. gitweb: Paginate project listJakub Narebski, May 10, 2008
  8. J.H.May 10, 2008
  9. Jakub NarebskiMay 10, 2008
  10. J.H.May 11, 2008
  11. Jakub NarebskiMay 11, 2008
  12. Jakub NarebskiMay 12, 2008
  13. Lars HjemliMay 12, 2008
  14. Jakub NarebskiMay 13, 2008
  15. Lars HjemliMay 13, 2008
  16. Jakub NarebskiMay 13, 2008
  17. Kristian HøgsbergMay 13, 2008
  18. Lars HjemliMay 13, 2008
  19. Jakub NarebskiMay 13, 2008
  20. Jakub NarebskiMay 14, 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.