- Sort Score
- Result 10 results
- Languages All
Results 631 - 640 of 658 for stacking (0.06 sec)
-
helm-releases/minio-3.5.1.tgz
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 with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies parameter values while installing the chart. For example, ```bash helm install --name my-release -f values.yaml minio/minio ``` Persistence ---------- This chart provisions...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Feb 04 22:54:20 UTC 2022 - 15.4K bytes - Viewed (0) -
helm-releases/minio-3.1.7.tgz
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 with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies parameter values while installing the chart. For example, ```bash helm install --name my-release -f values.yaml minio/minio ``` Persistence ---------- This chart provisions...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Oct 03 22:23:22 UTC 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.3.1.tgz
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 with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies parameter values while installing the chart. For example, ```bash helm install --name my-release -f values.yaml minio/minio ``` Persistence ---------- This chart provisions...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Dec 02 20:09:18 UTC 2021 - 14.6K bytes - Viewed (0) -
src/cmd/cgo/doc.go
to it. Whether Go memory is pinned is a dynamic property of that memory region; it has nothing to do with the type of the pointer. Go values created by calling new, by taking the address of a composite literal, or by taking the address of a local variable may also have their memory pinned using [runtime.Pinner]. This type may be used to manage the duration of the memory's pinned status, potentially beyond the
Registered: Tue Nov 05 11:13:11 UTC 2024 - Last Modified: Tue Oct 01 22:52:54 UTC 2024 - 44K bytes - Viewed (0) -
helm-releases/minio-3.4.3.tgz
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 with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies parameter values while installing the chart. For example, ```bash helm install --name my-release -f values.yaml minio/minio ``` Persistence ---------- This chart provisions...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Tue Dec 21 20:55:50 UTC 2021 - 17.7K bytes - Viewed (0) -
android/guava/src/com/google/common/collect/MapMakerInternalMap.java
* Read operations can thus proceed without locking, but rely on selected uses of volatiles to * ensure that completed write operations performed by other threads are noticed. For most * purposes, the "count" field, tracking the number of elements, serves as that volatile * variable ensuring visibility. This is convenient because this field needs to be read in many * read operations anyway: *
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Fri Oct 18 20:24:49 UTC 2024 - 90.8K bytes - Viewed (0) -
guava/src/com/google/common/collect/MapMakerInternalMap.java
* Read operations can thus proceed without locking, but rely on selected uses of volatiles to * ensure that completed write operations performed by other threads are noticed. For most * purposes, the "count" field, tracking the number of elements, serves as that volatile * variable ensuring visibility. This is convenient because this field needs to be read in many * read operations anyway: *
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Fri Oct 18 20:24:49 UTC 2024 - 90.8K bytes - Viewed (0) -
cmd/erasure-object.go
tgtClient, err := globalTierConfigMgr.getDriver(ctx, opts.Transition.Tier) if err != nil { return err } if !opts.NoLock { // Acquire write lock before starting to transition the object. lk := er.NewNSLock(bucket, object) lkctx, err := lk.GetLock(ctx, globalDeleteOperationTimeout) if err != nil { return err } ctx = lkctx.Context()
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Oct 31 22:10:24 UTC 2024 - 78.8K bytes - Viewed (0) -
src/bytes/bytes_test.go
Registered: Tue Nov 05 11:13:11 UTC 2024 - Last Modified: Mon Aug 19 19:09:04 UTC 2024 - 61.2K bytes - Viewed (0) -
doc/go_spec.html
<code>iota</code> represents successive untyped integer <a href="#Constants"> constants</a>. Its value is the index of the respective <a href="#ConstSpec">ConstSpec</a> in that constant declaration, starting at zero. It can be used to construct a set of related constants: </p> <pre> const ( c0 = iota // c0 == 0 c1 = iota // c1 == 1 c2 = iota // c2 == 2 ) const (
Registered: Tue Nov 05 11:13:11 UTC 2024 - Last Modified: Wed Oct 02 00:58:01 UTC 2024 - 282.5K bytes - Viewed (0)