Bug #16326

Updated by Ward Vandewege over 1 year ago

The detail on how to calculate MaxKeepBlobBuffers was accidentally dropped in the 2.0 doc update.

The description for MaxConcurrentRequests erroneously states that it is only used by Keepstore.

The description for MaxConcurrentRequests states that the default (0) means no limit, but in the Keepstore code, 0 is translated to 2 * MaxKeepBlobBuffers.

Back