- Sort Score
- Result 10 results
- Languages All
Results 31 - 40 of 89 for latency (0.03 sec)
-
docs/metrics/prometheus/grafana/replication/minio-replication-node.json
"interval": "1m", "intervalFactor": 2, "legendFormat": "{{server,endpoint}}", "refId": "A" } ], "title": "Avg. Link Latency (millis)", "type": "timeseries" }, { "datasource": { "type": "prometheus", "uid": "${DS_PROMETHEUS}" }, "fieldConfig": { "defaults": {
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Mon Aug 04 01:46:49 UTC 2025 - 57.5K bytes - Viewed (0) -
src/main/java/jcifs/internal/smb2/multichannel/ChannelLoadBalancer.java
} return maxBandwidthChannel != null ? maxBandwidthChannel : channels.iterator().next(); } if (isMetadataOperation(message)) { // For metadata operations, prefer low-latency channels return selectLeastLoaded(channels); } // Default to weighted random for general operations return selectWeightedRandom(channels); }Registered: Sat Dec 20 13:44:44 UTC 2025 - Last Modified: Sat Aug 30 05:58:03 UTC 2025 - 8.2K bytes - Viewed (0) -
cmd/metacache.go
// This will make `test/a` and `test/b` share listings if they are concurrent. // Enabling this will make cache sharing more likely and cause less IO, // but may cause additional latency to some calls. metacacheSharePrefix = false ) //go:generate msgp -file $GOFILE -unexported // metacache contains a tracked cache entry. type metacache struct {Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Fri Jul 12 16:23:16 UTC 2024 - 6K bytes - Viewed (0) -
docs/features/connections.md
server: the port number, HTTPS settings, and preferred network protocols (like HTTP/2). URLs that share the same address may also share the same underlying TCP socket connection. Sharing a connection has substantial performance benefits: lower latency, higher throughput (due to [TCP slow start](https://www.igvita.com/2011/10/20/faster-web-vs-tcp-slow-start/)) and conserved battery. OkHttp uses a [ConnectionPool](https://square.github.io/okhttp/4.x/okhttp/okhttp3/-connection-pool/) that automatically...
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Mon Feb 21 03:33:59 UTC 2022 - 5.4K bytes - Viewed (0) -
docs/metrics/prometheus/grafana/node/minio-node.json
"interval": "", "legendFormat": "[{{drive}}:{{api}}]", "refId": "B" } ], "title": "Drive Latency (micro sec)", "type": "timeseries" }, { "datasource": { "type": "prometheus", "uid": "${DS_PROMETHEUS}" }, "description": "", "fieldConfig": {
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Mon Aug 04 01:46:49 UTC 2025 - 22.5K bytes - Viewed (0) -
internal/kms/secret-key.go
} return &KMS{ Type: Builtin, DefaultKey: keyID, conn: secretKey{ keyID: keyID, key: key, }, latencyBuckets: defaultLatencyBuckets, latency: make([]atomic.Uint64, len(defaultLatencyBuckets)), }, nil } // secretKey is a KMS implementation that derives new DEKs // from a single key. type secretKey struct { keyID string key []byte }
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Mon Apr 21 16:23:51 UTC 2025 - 8.4K bytes - Viewed (0) -
README.md
efficiently makes your stuff load faster and saves bandwidth. OkHttp is an HTTP client that’s efficient by default: * HTTP/2 support allows all requests to the same host to share a socket. * Connection pooling reduces request latency (if HTTP/2 isn’t available). * Transparent GZIP shrinks download sizes. * Response caching avoids the network completely for repeat requests.
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Thu Oct 30 21:39:59 UTC 2025 - 9.5K bytes - Viewed (0) -
internal/grid/README.md
It includes built in muxing of concurrent requests as well as congestion handling for streams. Requests can be "Single Payload" or "Streamed". Use the MinIO Grid for: * Small, frequent requests with low latency requirements. * Long-running requests with small/medium payloads. Do *not* use the MinIO Grid for: * Large payloads. Only a single connection is ever made between two servers.
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Fri Oct 10 18:57:03 UTC 2025 - 9.4K bytes - Viewed (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/OkHttpClient.kt
* OkHttp performs best when you create a single `OkHttpClient` instance and reuse it for all of * your HTTP calls. This is because each client holds its own connection pool and thread pools. * Reusing connections and threads reduces latency and saves memory. Conversely, creating a client * for each request wastes resources on idle pools. * * Use `new OkHttpClient()` to create a shared instance with the default settings: * * ```java
Registered: Fri Dec 26 11:42:13 UTC 2025 - Last Modified: Tue Oct 07 21:55:03 UTC 2025 - 51.4K bytes - Viewed (0) -
cmd/metacache-stream.go
blockSize int streamWg sync.WaitGroup reuseBlocks bool } // newMetacacheWriter will create a serializer that will write objects in given order to the output. // Provide a block size that affects latency. If 0 a default of 128KiB will be used. // Block size can be up to 4MiB. func newMetacacheWriter(out io.Writer, blockSize int) *metacacheWriter { if blockSize < 8<<10 { blockSize = 128 << 10 } w := metacacheWriter{
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Wed May 07 15:37:12 UTC 2025 - 19.5K bytes - Viewed (0)