RE: Re: Repo-Browser Usability

Hi Steven,

1) I am sorry, what I meant is that the performance problem os "obvious" and "real". I am not shure if it is fully analysed, or even if it needs additional svn core functionality since it probably needs a server side service.

2) Thank you for the hint about the tsvn: protokoll links. I'll go further that path. I already created in cron a page via svn list --xml and convert it with a java tool.

To explain the need: Some of our svn directories have 2GB some only few MB. If a user is connected trough a slow ADSL Line and tries to check out a huge Directory or updates item to revision, he is not aware of the time needed for the operation. He tries to check out but, this is going to last hours... but he has to leave, or any other reason to disconnect.

My collegues are mainly using tsvn for their daily work. And they are very pleased with. They are just continously asking, why they have to check the size/nb of files in a web browser and then going to "update to rev"/"check out" whilst TSVN has its own browser.

The repository has ~300GB / ~400.000 Files / ~15.000 revs.

regards
Thomas

> On 24.06.2011 08:42, Thomas STümpfig wrote:
> > Hi everybody, is there a way to see easily the recusive filecount and
> > the total filesize wihtin tsvn?
>
> No, sorry.
>
> > I am aware of an older discussion about this. Within huge
> > repositories it is sometimes necessary to roughly check upfront how
> > long a checkout would need.
> >
> > We use svn for document management, and only partialy for scm. Tsvn
> > is the front end for our consultants.
> >
> > There are ways to do this via svn list -xml .... | script to parse
> > ..., my collegues ask for configurable, colums in the repobrowser.
> >
> > The performance issue is clear! Probably could be mitigated through
> > caching like tsvn is doing for log-caching.
> >
> > i appreciate your comments.
>
> I'm sorry, but even though you say that the "performance issue is clear"
> you haven't really thought this through. The performance issue is real -
> for example, doing that for the TSVN repository on trunk takes more than
> 10 minutes. I'm pretty sure that none of your users would accept that -
> it might be faster to just start the checkout.
>
> Now, why don't you set up a web page with that kind of information? You
> could write a script directly on the server that fetches that
> information (much, much faster that way) and generate a html page with
> that info. Users then can easily see it, and if you also provide tsvn
> checkout links [1] from there it would be even better :).
>
> [1]
> http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-repository-links.html
>
> Stefan
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2778019

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-06-27 09:21:55 CEST