@@ -382,6 +382,50 @@ adjustments mid-transfer command in order to increase throughput and reach the
382
382
requested bandwidth.
383
383
384
384
385
+ should_stream
386
+ -------------
387
+ .. note ::
388
+ This configuration option is only supported when the ``preferred_transfer_client ``
389
+ configuration value is set to or resolves to ``crt ``. The ``classic `` transfer
390
+ client does not support this configuration option.
391
+
392
+ **Default ** - ``false ``
393
+
394
+ If set to ``true ``, the CRT client will skip buffering parts in-memory before
395
+ sending PUT requests.
396
+
397
+
398
+ disk_throughput
399
+ ---------------
400
+ .. note ::
401
+ This configuration option is only supported when the ``preferred_transfer_client ``
402
+ configuration value is set to or resolves to ``crt ``. The ``classic `` transfer
403
+ client does not support this configuration option.
404
+
405
+ **Default ** - ``10.0 ``
406
+
407
+ The estimated target disk throughput. This value is only applied if
408
+ ``should_stream `` is set to ``true ``.This value can be specified using
409
+ the same semantics as ``target_throughput ``, that is either as the
410
+ number of bytes per second as an integer, or using a rate suffix.
411
+
412
+
413
+ direct_io
414
+ ---------
415
+ .. note ::
416
+ This configuration option is only supported when the ``preferred_transfer_client ``
417
+ configuration value is set to or resolves to ``crt ``. The ``classic `` transfer
418
+ client does not support this configuration option.
419
+
420
+ .. note ::
421
+ This configuration option is only supported on Linux.
422
+
423
+ **Default ** - ``false ``
424
+
425
+ If set to ``true ``, the CRT client will enable direct IO to bypass the OS
426
+ cache when sending PUT requests. Enabling direct IO may be useful in cases
427
+ where the disk IO outperforms the kernel cache.
428
+
385
429
Experimental Configuration Values
386
430
=================================
387
431
0 commit comments