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

Re: sync() slowdown

From
Matthieu Moy <matthieu.moy@imag.fr>
Date
May 26, 2008, 16:09 UTC
Message-ID
<vpq1w3p59ns.fsf@bauges.imag.fr>
In-Reply-To
<20080526142607.GA3082@kali.thurne.chezwam.org>
Sebastien Gross <seb-git@chezwam.org> writes:
> I think this might be useful if you repack many repositories.
> If you call the sync command before looping the repacks I guess this
> could be equivalent (modulo changes done in repositories during that
> time).
I suppose git-repack does something like

write_new_data(); sync(); delete_old_data();

And if you remove the "sync" and your system crashes (or you eject your USB key, or ...) while "delete_old_data" is done, but "write_new_data" hasn't been sync-ed to the hard disk, you're in trouble.

If you repack many repositories, I guess the first time is expansive, but the next ones pay only for what they just did.

My 2 cents,
-- 
Matthieu
Previous: Sebastien Gross
Message 4 of 4 in “sync() slowdown”
  1. Sebastien GrossMay 26, 2008
  2. Kenneth P. TurveyMay 26, 2008
  3. Sebastien GrossMay 26, 2008
  4. Matthieu MoyMay 26, 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.