]> source.dussan.org Git - jgit.git/commit
DHT: Always have at least one recent chunk in DhtReader 06/3706/1
authorShawn O. Pearce <spearce@spearce.org>
Fri, 10 Jun 2011 00:55:52 +0000 (17:55 -0700)
committerShawn O. Pearce <spearce@spearce.org>
Fri, 10 Jun 2011 00:55:52 +0000 (17:55 -0700)
commit57853e494972e7a9a6248648fd9f8479844c5348
tree529fa00c959891e040ade860b1e5790197a22912
parentd00f527d659c9eb1fabc434b45f94b98e221c509
DHT: Always have at least one recent chunk in DhtReader

The RecentChunks cache assumes there is always at least one recent
chunk in the maxSize that it receives from the DhtReaderOptions.
Ensure that is true by requiring the size to be at least 1.

Running with 0 recent chunk cache is very a bad idea, often
during commit walking the parents of a commit will be found
on the same chunk as the commit that was just accessed. In
these cases its a good idea to keep that last chunk around
so the parents can be quickly accessed.

Change-Id: I33b65286e8a4cbf6ef4ced28c547837f173e065d
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
org.eclipse.jgit.storage.dht/src/org/eclipse/jgit/storage/dht/DhtReaderOptions.java