- Sort Score
- Result 10 results
- Languages All
Results 1 - 9 of 9 for Compact (6.05 sec)
-
manifests/charts/gateway/README.md
For consistency, the same profiles are used across each chart, even if they do not impact a given chart. Explicitly set values have highest priority, then profile settings, then chart defaults. As an implementation detail of profiles, the default values for the chart are all nested under `defaults`.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 19:38:07 GMT 2024 - 6.6K bytes - Viewed (0) -
docs/config/README.md
scanner can be adjusted by the `mc admin config set alias/ delay=15.0`. By default the value is `10.0`. This means the scanner will sleep *10x* the time each operation takes. In most setups this will keep the scanner slow enough to not impact overall system performance. Setting the `delay` key to a *lower* value will make the scanner faster and setting it to 0 will make the scanner run at full speed (not recommended in production). Setting it to a higher value will make the scanner slower,...
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Sep 11 21:48:54 GMT 2023 - 17.7K bytes - Viewed (0) -
manifests/charts/ztunnel/README.md
For consistency, the same profiles are used across each chart, even if they do not impact a given chart. Explicitly set values have highest priority, then profile settings, then chart defaults. As an implementation detail of profiles, the default values for the chart are all nested under `defaults`.
Plain Text - Registered: Wed Mar 20 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 1.3K bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/README.md
For consistency, the same profiles are used across each chart, even if they do not impact a given chart. Explicitly set values have highest priority, then profile settings, then chart defaults. As an implementation detail of profiles, the default values for the chart are all nested under `defaults`.
Plain Text - Registered: Wed Mar 20 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 2K bytes - Viewed (0) -
manifests/charts/istio-cni/README.md
For consistency, the same profiles are used across each chart, even if they do not impact a given chart. Explicitly set values have highest priority, then profile settings, then chart defaults. As an implementation detail of profiles, the default values for the chart are all nested under `defaults`.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 2.5K bytes - Viewed (0) -
docs/erasure/storage-class/README.md
saving the object in specific number of data and parity drives. ## Storage usage The selection of varying data and parity drives has a direct impact on the drive space usage. With storage class, you can optimize for high redundancy or better drive space utilization.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Aug 15 23:04:20 GMT 2023 - 5.8K bytes - Viewed (1) -
manifests/charts/base/README.md
For consistency, the same profiles are used across each chart, even if they do not impact a given chart. Explicitly set values have highest priority, then profile settings, then chart defaults. As an implementation detail of profiles, the default values for the chart are all nested under `defaults`.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 1.3K bytes - Viewed (0) -
docs/compression/README.md
which is a fitness factor for a lossless data compression. Pre-compressed input typically compresses in excess of 2GiB/s per core, so performance impact should be minimal even if precompressed data is re-compressed. Decompressing incompressible data has no significant performance impact. Below is a list of common files and content-types which are typically not suitable for compression. - Extensions | `gz` | (GZIP) |
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Mar 11 11:55:34 GMT 2024 - 5.1K bytes - Viewed (0) -
docs/distributed/README.md
> **NOTE:** `{1...n}` shown have 3 dots! Using only 2 dots `{1..n}` will be interpreted by your shell and won't be passed to MinIO server, affecting the erasure coding order, which would impact performance and high availability. **Always use ellipses syntax `{1...n}` (3 dots!) for optimal erasure-code distribution** ### Expanding existing distributed setup
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 8.8K bytes - Viewed (0)