Re: Faster revision graphs

> No, everything is standard.  When I started SmartSVN6 for the first time, it
> took about 2 minutes before the splash screen came up.  While waiting, I
> checked my user directory and saw that it was copying my repository and
> project profiles over from 5 directory to new 6 directory.  Splash screen came
> up with no warning about rebuilding log caches.  No problem I will rebuild
> them.
>
> ---
> Shawn Castrianni
>
> From: smartsvn@... [mailto:smartsvn@...] On Behalf Of
> syntevo Support
> Sent: Monday, June 08, 2009 2:28 AM
> To: smartsvn@...
> Subject: Re: [smartsvn] Faster revision graphs
>
>
>
>
>
> > By the way, none of my log cache was migrated when I ran SmartSVN 6 for the
> > first time. I can still see it sitting in my 5’s log-cache folder while my
> > 6’s log-cache folder is empty. Do I have to rebuild my log-cache when
> > upgrading from 5->6?
>
> SmartSVN's Log Cache format has changed since the first 6 beta version, so it
> should have reported that Log Caches have to be rebuilt. Are you maybe using
> portable bundle which stores settings in the installation directory or is
> smartsvn.home pointing to somewhere else?
>
> --
> Best regards,
> Marc Strapetz
> _____________
> syntevo GmbH
> www.syntevo.com
>
> Shawn Castrianni
> <Shawn.Castrianni@...<mailto:Shawn.Castrianni%40halliburton.com>>
> wrote:
>
> > Wonderful!
> >
> > By the way, none of my log cache was migrated when I ran SmartSVN 6 for the
> > first time. I can still see it sitting in my 5’s log-cache folder while my
> > 6’s log-cache folder is empty. Do I have to rebuild my log-cache when
> > upgrading from 5->6?
> >
> > ---
> > Shawn Castrianni
> >
> > From: smartsvn@...<mailto:smartsvn%40yahoogroups.com> [mailto:smartsvn@...<mailto:smartsvn%40yahoogroups.com>] On Behalf Of
> > syntevo Support
> > Sent: Sunday, June 07, 2009 2:36 AM
> > To: smartsvn@...<mailto:smartsvn%40yahoogroups.com>
> > Subject: Re: [smartsvn] Faster revision graphs
> >
> >
> >
> >
> >
> > > So I was wondering, until SVN fixes its architecture with Copy-To links,
> > > can you do anything more with SmartSVN to improve the revision graph
> > > generation?
> >
> > Thanks for your ideas. For 6.1 there will be improvements in Log Cache
> > performance which should also make Revision Graphs significantly faster.
> >
> > --
> > Best regards,
> > Marc Strapetz
> > _____________
> > syntevo GmbH
> > www.syntevo.com
> >
> > Shawn Castrianni
> > <Shawn.Castrianni@...<mailto:Shawn.Castrianni%40halliburton.com><mailto:Shawn.Castrianni%40halliburton.com>>
> > wrote:
> >
> > > I realize that SVN has a significant architecture flaw (in my opinon) to only
> > > store Copy-From links instead of both Copy-From and Copy-To links. Therefore,
> > > any revision graph command must play back the entire transaction history
> > > looking for branch points to properly draw the graph. I also realize that you
> > > keep a cache of the full transaction history to speed up this revision graph,
> > > branch point search. However, the speed of generating these revision graphs
> > > in SmartSVN is nothing like SmartCVS where the CVS architecture is more
> > > efficient in this area. I was curious what you actually store in the
> > > transaction history cache. I would think that if you generated Copy-To links
> > > inside your private SmartSVN transaction history cache, that you could then
> > > generate revision graphs very quickly. I am assuming that you do NOT generate
> > > these Copy-To links making your revision graphs still a little slow.
> > >
> > > So I was wondering, until SVN fixes its architecture with Copy-To links, can
> > > you do anything more with SmartSVN to improve the revision graph generation?
> > > Can you scan the transaction history after you have cached it and generate
> > > Copy-To links as part of the cache?
> > >
> > > ---
> > > Shawn Castrianni
> > >
> > > ----------------------------------------------------------
> > > This e-mail, including any attached files, may contain confidential and
> > > privileged information for the sole use of the intended recipient. Any
> > > review, use, distribution, or disclosure by others is strictly prohibited. If
> > > you are not the intended recipient (or authorized to receive information for
> > > the intended recipient), please contact the sender by reply e-mail and delete
> > > all copies of this message.
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > > Yahoo! Groups Links
> > >
> > >
> > >
> > >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>