Ability to to perform re-index with a quota on time / memory consumption
|Reported by:||Patrick Martin||Owned by:||anonymous|
I don't think this is an easy one, but the time and resources required to re-index a large number of changes are quite significant.
Is it possible for a re-index to index a configurable number of files on each invocation? This would leave the repository search out of date, but release the server to serve the requests of other users. Susbsequent re-indexes could fill in the gap.
I'm not sure how valuable this would be if #365 were implemented, as one huge cost to re-indexing (tagging and branching) could be radically reduced. Nonetheless, repository search is transparently such a great feature is would be a shame if it became a victim of its own success when people with large-ish source trees (>1K files) have a go at using it.
Change History (9)
comment:5 Changed 7 years ago by
|Owner:||changed from Alec Thomas to Ryan J Ollos|
|Status:||assigned → new|
comment:6 Changed 7 years ago by
|Summary:||ability to to perform re-index with a quota of time / memory consumption → Ability to to perform re-index with a quota on time / memory consumption|