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

Re: oprofile on svn import

From
Jon Smirl <jonsmirl@gmail.com>
Date
Jun 14, 2006, 02:39 UTC
Message-ID
<9e4733910606131939h35b2278bvaa296459ea061621@mail.gmail.com>
In-Reply-To
<20060614020108.GB12083@hand.yhbt.net>
On 6/13/06, Eric Wong <normalperson@yhbt.net> wrote:
Show 9 quoted lines
> Jon Smirl <jonsmirl@gmail.com> wrote:
> > I'm going back to cvsimport tomorrow. My svn import that had been
> > running for five days got killed this morning when the city decided to
> > move the telephone pole that provides my electricty.
> >
> > Some oprofile data, this doesn't make a lot of sense to me. Why is it
> > in libcypto so much?
>
> The sha1 calculation is done in libcrypto, afaik.
That make sense, but it's eating up 14% of my CPU in a long sample.
> Anybody want to see how my latest patches to git-svn (and using SVN perl
> libraries) stacks up against the mozilla repo?  Speedwise, I don't
> expect git-svn to be too different than git-svnimport, but it should use
> much less memory (I'll probably port the hacks to git-svnimport, too).

Can svnimport be rewritten to avoid calling fork? If I am reading the oprofiles correctly that fork is very expensive especially when the svnimport task grows to 600MB.

I have an import running but post your code when it is ready and I can try it on the next run. They always seem to fail so there will probably be another run.

Show 7 quoted lines
> I'll see about freeing up one of my machines to test the mozilla repo.
> Unfortunately, all of my hardware is a few years old and not extremely
> fast.
>
> --
> Eric Wong
>
-- 
Jon Smirl
jonsmirl@gmail.com
Previous: Eric WongNext: Eric Wong
Message 3 of 10 in “oprofile on svn import”
  1. Jon SmirlJun 14, 2006
  2. Eric WongJun 14, 2006
  3. Jon SmirlJun 14, 2006
  4. Eric WongJun 14, 2006
  5. Ryan AndersonJun 14, 2006
  6. Jon SmirlJun 14, 2006
  7. Jon SmirlJun 14, 2006
  8. Jon SmirlJun 14, 2006
  9. Jakub NarebskiJun 14, 2006
  10. Martin LanghoffJun 14, 2006

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.