I mean every different TortoiseSVN command -- including TortoiseSVN >>
Settings which I just tried when I went to look at the cache settings as
you suggested. One other new piece of information. When I tried Settings
and Show Log just now, the CPU did *not* show any unusual increase, yet
each operation still took 15 to 20 seconds before it opened a dialog window.
On Fri, Feb 17, 2012 at 2:13 PM, Simon Large <simon.tortoisesvn_at_gmail.com>wrote:
> On 17 February 2012 00:01, michael sorens <birdwatcher42_at_gmail.com> wrote:
> > I am writing a series of articles on Subversion and TortoiseSVN
> published on
> > Simple-Talk.com (latest one here). I am working on a section about
> > Collabnet's Subversion Edge so I generated a fresh Win7 VM and installed
> > Edge as well as TortoiseSVN. The web interface to the Subversion server
> > responds promptly as expected. As does the command line interface (e.g.
> > log <file>). But attempting to do a show log on the same file from
> > TortoiseSVN's context menu slams my CPU utilization to 100% and the
> > operation takes anywhere from 12 to 20 seconds to complete. Checking the
> > Apache logs confirms that it is likely a client-side issue with
> > TortoiseSVN--the Apache logs do not show anything until the end of the
> > period. Note that this delay is present with every TortoiseSVN command.
> > repeating the same command twice shows no caching effect; the second try
> > takes just as long. Any rhyme or reason to this...?
> When you say every command, you mean Update, Diff, Update to Revision,
> etc.? Or do you just mean every time you use TSVN->Show Log?
> Note that the equivalent svn command would be svn st -v URL. The -v
> makes a big difference.
> The reason for the high CPU might be the access to the log cache. You
> could try clearing or disabling the log cache and then you would see
> the server being hit right away.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-02-20 22:57:12 CET