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

Re: Better value for chunk_size when threaded

From
Andreas Ericsson <ae@op5.se>
Date
Dec 7, 2007, 08:57 UTC
Message-ID
<47590AEE.2080705@op5.se>
In-Reply-To
<9e4733910712061558k19fbc864ia1fb7a3431fd2603@mail.gmail.com>
Jon Smirl wrote:
Show 11 quoted lines
> I tried some various ideas out for chunk_size and the best strategy I
> found was to simply set it to a constant. How does 20,000 work on
> other CPUs?
> 
> I'd turn on default threaded support with this change. With threads=1
> versus non-threaded there is no appreciable difference in the time.
> 
> Is there an API to ask how many CPUs are in the system? It would be
> nice to default the number of threads equal to the number of CPUs and
> only use pack.threads=X to override.
> 

I posted a patch to implement that just yesterday. It might need some polishing, but it hasn't received any comments so far.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231
Previous: Nicolas Pitre
Message 7 of 7 in “Better value for chunk_size when threaded”
  1. Jon SmirlDec 6, 2007
  2. Nicolas PitreDec 7, 2007
  3. Jon SmirlDec 7, 2007
  4. Nicolas PitreDec 7, 2007
  5. Andreas EricssonDec 10, 2007
  6. Nicolas PitreDec 10, 2007
  7. Andreas EricssonDec 7, 2007

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.