Retrieving Repository Structure Info
"Anthony Davis" <[email protected]> Tue, 27 Apr 2004 15:29:15 -0600
| Newsgroups | gmane.comp.version-control.sourcegear-vault.user |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
------_=_NextPart_001_01C42C9E.B23BD6B3
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
On our large repository, retrieving repository structure info is taking
a very very long time. The pattern is that first the server thinks
about it for about 1.5 minutes, the data is nearly instantaneously
transferred, then the client thinks about it for about 30 seconds (full
processor load). I have visions of the world's largest bubble sort
happening when we get the files. =20
=20
We're buying a much better server for Vault to run on (should be very
nice), and I promise that the gold support PO will be on its way soon
:-) . Hopefully the server (dual 3 GHz with 4 GB ram) will be
sufficient. We have 25 users, so things do get busy. The ol' P3 was
having issues.
=20
But my concern is really about the client side processing. Is there
something we can do to help this out? Typically the answer is to get
the overall node count of the repository down. It would be really great
if we could send things to other repositories. Also, a way to convert
old style snapshots into new labels would be very nice (we love the
snapshots, but for many things, we were using them when a label would
really be better.) =20
=20
So I guess, bottom line, I'd like to have:
=20
A) This operation a bit more optimized on both ends.
B) Way to move whole trees of data to other repositories.
C) Way to convert snapshots to labels
D) (I didn't talk about this) A way to recursively obliterate.
Will it speed things up if data is obliterated? I have problems
obliterating things because it always says I have to obliterate
something else, and that annoys me. =20
=20
Tony
=20
------_=_NextPart_001_01C42C9E.B23BD6B3
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1195078348;
mso-list-type:hybrid;
mso-list-template-ids:1535311462 -1466650666 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:alpha-upper;
mso-level-text:"%1\)";
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>On our large repository, retrieving repository =
structure
info is taking a very very long time. The pattern is that first =
the server
thinks about it for about 1.5 minutes, the data is nearly =
instantaneously
transferred, then the client thinks about it for about 30 seconds (full
processor load). I have visions of the world’s largest =
bubble sort
happening when we get the files. <o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>We’re buying a much better server for Vault to =
run on
(should be very nice), and I promise that the gold support <st1:place =
w:st=3D"on">PO</st1:place>
will be on its way soon </span></font><font size=3D2 =
face=3DWingdings><span
style=3D'font-size:10.0pt;font-family:Wingdings'>J</span></font><font =
size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'> . =
Hopefully the
server (dual 3 GHz with 4 GB ram) will be sufficient. We have 25 =
users, so
things do get busy. The ol’ P3 was having =
issues.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>But my concern is really about the client side =
processing.
Is there something we can do to help this out? Typically the =
answer is to get
the overall node count of the repository down. It would be really =
great if we
could send things to other repositories. Also, a way to convert =
old style
snapshots into new labels would be very nice (we love the snapshots, but =
for
many things, we were using them when a label would really be =
better.) <o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>So I guess, bottom line, I’d like to =
have:<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>A)<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'> =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>This
operation a bit more optimized on both =
ends.<o:p></o:p></span></font></p>
<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>B)<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'> =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Way to move
whole trees of data to other repositories.<o:p></o:p></span></font></p>
<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>C)<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'> =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Way to
convert snapshots to labels<o:p></o:p></span></font></p>
<p class=3DMsoNormal =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><span
style=3D'mso-list:Ignore'>D)<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'> =
</span></font></span></span></font><![endif]><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>(I didn’t
talk about this) A way to recursively obliterate. Will it speed =
things up if
data is obliterated? I have problems obliterating things because =
it always
says I have to obliterate something else, and that annoys me. =
<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Tony<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
</div>
</body>
</html>
------_=_NextPart_001_01C42C9E.B23BD6B3--