Re: oprofile on svn import

On 6/13/06, Eric Wong [off-list ref] wrote:

Jon Smirl [off-list ref] wrote:

quoted

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.

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