kesavanpos / tortoisesvn

Automatically exported from code.google.com/p/tortoisesvn
0 stars 0 forks source link

Prefetch log info #7

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
For all log caches, the system shall poll the respective repositories for
new log info. Missing data is then fetched and written to the cache. The
goal is to make the log display instantaneous.

The following has to be implemented:

* the update interval shall be configurable.
  Default is 250 seconds, i.e. slightly below the default
  MaxHeadAge.
* if the access fails, the respective repository
  will not be contacted again for a pre-configured
  period of time. Default: 3600 seconds.
* the user shall be able to disable the auto-update per 
  repository (i.e. log cache file)
* at most 100 entries will be fetched per query
* HEAD lookup & cache update will be done on the common
  base folder of all cached changes
* caches that are currently used (i.e. locked) shall not
  be updated

May be implemented similar to or even as a part of TSVNCache.

Original issue reported on code.google.com by stefan.f...@gmail.com on 18 Mar 2010 at 7:12

GoogleCodeExporter commented 9 years ago
Since this would put a lot of stress on the repository servers, I'd say the 
default
must be 'disabled' for that feature.
Otherwise sourceforge/tigris/... will shoot us on sight next time they see us.

And maybe even use the svnrobots.txt file CommitMonitor uses:
http://tools.tortoisesvn.net/svnrobots

Original comment by tortoisesvn on 18 Mar 2010 at 7:43

GoogleCodeExporter commented 9 years ago
Right. To limit the impact on repository servers,
the following shall be implemented in addition to
the initial list of items:

* feature is strictly opt-in. A list of URL patterns
  must be specified to activate it (so, activating 
  it for all LAN servers is simple)
* honour svnrobots.txt as described by above link
* don't update the log cache if the log has not been
  used by TSVN for a configurable amount of time.
  Default: 1 week. 

Original comment by stefan.f...@gmail.com on 20 Mar 2010 at 10:34

GoogleCodeExporter commented 9 years ago
Since the project monitor (issue #652) monitors projects and fetches the log if 
new commits are detected, I'd say this issue is basically done now.

Original comment by tortoisesvn on 5 Dec 2014 at 5:42