[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-dev
Subject:    Fwd: Effects of importing over 18000 items into repository as one commit transaction
From:       Pavel Repin <prepin () gmail ! com>
Date:       2005-11-30 20:46:10
Message-ID: 4b217830511301246v35e37716w9c6c80c0cd2d8b06 () mail ! gmail ! com
[Download RAW message or body]

This did not result in any response on the users list.
Hopefully someone among svn hackers might know about the impacts of a
largish commit.

---------- Forwarded message ----------
From: Pavel Repin <prepin@gmail.com>
Date: Nov 29, 2005 8:18 AM
Subject: Effects of importing over 18000 items into repository as one commi=
t
transaction
To: users@subversion.tigris.org

Hi svn users,

We are rolling out a subversion install at work.
One of the teams created a FSFS repository and svn-imported a snapshot of
their entire source tree in one transaction. The resulting FSFS revision
file "1" is 261 MB and contains 18834 items. Do you think that was a bad
idea to import the entire tree in one shot?

I sort of suspect it was a bad idea because I am noticing that "svn log"
takes considerable amount of time before it dumps anything to stdout on a
repository that had only 35 checkins so far.
I've seen much better "svn log" performance on a repository with vastly
larger number of checked in revisions, but that repository grew naturally
(it started from nothing and it grew little by little with each checkin).

Should we have imported that tree as a set of smaller checkins?
Any suggestions or hints will be very helpful.

--
Pavel Repin

[Attachment #3 (text/html)]

This did not result in any response on the users list.<br>Hopefully someone among svn \
hackers might know about the impacts of a largish commit.<br><br>---------- Forwarded \
message ----------<br><span class="gmail_quote">From:  <b \
class="gmail_sendername">Pavel Repin</b> &lt;<a \
href="mailto:prepin@gmail.com">prepin@gmail.com</a>&gt;<br>Date: Nov 29, 2005 8:18 \
AM<br>Subject: Effects of importing over 18000 items into repository as one commit \
transaction <br>To: <a \
href="mailto:users@subversion.tigris.org">users@subversion.tigris.org</a><br><br></span>Hi \
svn users,<br> <br>
We are rolling out a subversion install at work.<br>
One of the teams created a FSFS repository and svn-imported a snapshot
of their entire source tree in one transaction. The resulting FSFS
revision file &quot;1&quot; is 261 MB and contains 18834 items. Do you think that
was a bad idea to import the entire tree in one shot?<br>
<br>
I sort of suspect it was a bad idea because I am noticing that &quot;svn
log&quot; takes considerable amount of time before it dumps anything to
stdout on a repository that had only 35 checkins so far. <br>
I've seen much better &quot;svn log&quot; performance on a repository with vastly
larger number of checked in revisions, but that repository grew
naturally (it started from nothing and it grew little by little with
each checkin).<br>
<br>
Should we have imported that tree as a set of smaller checkins?<br>
Any suggestions or hints will be very helpful.<br clear="all"><br>-- <br><span \
class="sg">Pavel Repin

</span><br clear="all"><br>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic