if autotune {
		newConcurrent := concurrent + (concurrent+1)/2
		autoTunedCapacityNeeded := uint64(newConcurrent * size)
		if capacity < autoTunedCapacityNeeded {
			// Turn-off auto-tuning if next possible concurrency would reach beyond disk capacity.
			return true, false, ""
		}
	}

	return true, autotune, ""
}

// DriveSpeedtestHandler - reports throughput of drives available in the cluster

-f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server...

        evictEntries(newEntry);
        return null;
      } finally {
        unlock();
        postWriteCleanup();
      }
    }

    /** Expands the table if possible. */
    @GuardedBy("this")
    void expand() {
      AtomicReferenceArray<ReferenceEntry<K, V>> oldTable = table;
      int oldCapacity = oldTable.length();
      if (oldCapacity >= MAXIMUM_CAPACITY) {

old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server...

old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server...

old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server...

old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server...

-f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server...

				Name:     "README",
				Content:  []byte("This small file is in ZIP64 format.\n"),
				Modified: time.Date(2012, 8, 10, 14, 33, 32, 0, timeZone(-4*time.Hour)),
				Mode:     0644,
			},
		},
	},
	// Largest possible non-zip64 file, with no zip64 header.
	{
		Name:   "big.zip",
		Source: returnBigZipBytes,
		File: []ZipTestFile{
			{
				Name:     "big.file",
				Content:  nil,
				Size:     1<<32 - 1,

-f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server...