Project

General

Profile

Actions

Bug #16326

closed

[doc] improve MaxConcurrentRequests and MaxKeepBlobBuffers descriptions

Added by Ward Vandewege about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Story points:
-
Release relationship:
Auto

Description

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.


Subtasks 1 (0 open1 closed)

Task #16327: ReviewResolvedTom Clegg04/09/2020Actions
Actions

Also available in: Atom PDF