Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 6 of 6 for Throttle (0.04 sec)

  1. internal/bucket/bandwidth/reader.go

    type MonitorReaderOptions struct {
    	BucketOptions
    	HeaderSize int
    }
    
    // Read implements a throttled read
    func (r *MonitoredReader) Read(buf []byte) (n int, err error) {
    	if r.throttle == nil {
    		return r.r.Read(buf)
    	}
    	if r.lastErr != nil {
    		err = r.lastErr
    		return
    	}
    	b := r.throttle.Burst()  // maximum available tokens
    	need := len(buf)         // number of bytes requested by caller
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Fri Jul 12 14:57:31 UTC 2024
    - 3.2K bytes
    - Viewed (0)
  2. internal/bucket/bandwidth/monitor.go

    	limitBytes := limit / int64(m.NodeCount)
    	throttle, ok := m.bucketsThrottle[BucketOptions{Name: bucket, ReplicationARN: arn}]
    	if !ok {
    		throttle = &bucketThrottle{}
    	}
    	throttle.NodeBandwidthPerSec = limitBytes
    	throttle.Limiter = rate.NewLimiter(rate.Limit(float64(limitBytes)), int(limitBytes))
    	m.bucketsThrottle[BucketOptions{Name: bucket, ReplicationARN: arn}] = throttle
    }
    
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Mon Feb 19 22:54:46 UTC 2024
    - 6K bytes
    - Viewed (0)
  3. docs/throttle/README.md

    MinIO server allows to throttle incoming requests:
    
    - limit the number of active requests allowed across the cluster
    - limit the wait duration for each request in the queue
    
    These values are enabled using server's configuration or environment variables.
    
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Fri Aug 16 08:43:49 UTC 2024
    - 1.5K bytes
    - Viewed (1)
  4. docs/contribute/concurrency.md

    Framing rules make it impractical to implement http/2 correctly on a single blocking thread. The flow-control features introduce feedback between reads and writes, requiring writes to acknowledge reads and reads to throttle writes.
    
    In OkHttp we expose a blocking API over a framed protocol. This document explains the code and policy that makes that work.
    
    ### Threads
    
    #### Application's calling thread
    
    Registered: Fri Nov 01 11:42:11 UTC 2024
    - Last Modified: Sun Feb 06 16:35:36 UTC 2022
    - 7K bytes
    - Viewed (0)
  5. mockwebserver/src/main/kotlin/mockwebserver3/internal/ThrottledSink.kt

     * limitations under the License.
     *
     */
    package mockwebserver3.internal
    
    import okio.Buffer
    import okio.Sink
    
    /**
     * A sink that sleeps [periodDelayNanos] every [bytesPerPeriod] bytes. Unlike [okio.Throttler],
     * this permits any interval to be used.
     */
    internal class ThrottledSink(
      private val delegate: Sink,
      private val bytesPerPeriod: Long,
      private val periodDelayNanos: Long,
    ) : Sink by delegate {
    Registered: Fri Nov 01 11:42:11 UTC 2024
    - Last Modified: Mon Jan 08 01:13:22 UTC 2024
    - 1.5K bytes
    - Viewed (0)
  6. mockwebserver/src/main/kotlin/mockwebserver3/Dispatcher.kt

       * be received. The default implementation returns an empty response. Mischievous implementations
       * can return other values to test HTTP edge cases, such as unhappy socket policies or throttled
       * request bodies.
       */
      open fun peek(): MockResponse {
        return MockResponse(socketPolicy = KeepOpen)
      }
    
      /**
    Registered: Fri Nov 01 11:42:11 UTC 2024
    - Last Modified: Tue Jan 23 14:31:42 UTC 2024
    - 1.7K bytes
    - Viewed (0)
Back to top