Search Options

Results per page
Sort
Preferred Languages
Advance

Results 11 - 13 of 13 for leaks (0.24 sec)

  1. internal/handlers/forwarder.go

    	}
    
    	return f
    }
    
    type bufPool struct {
    	sz   int
    	pool sync.Pool
    }
    
    func (b *bufPool) Put(buf []byte) {
    	if cap(buf) < b.sz || cap(buf) > b.sz*2 {
    		// Buffer too small or will likely leak memory after being expanded.
    		// Drop it.
    		return
    	}
    	b.pool.Put(&buf)
    }
    
    func (b *bufPool) Get() []byte {
    	bufp := b.pool.Get().(*[]byte)
    	return (*bufp)[:b.sz]
    }
    
    Go
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Fri Apr 07 05:42:10 GMT 2023
    - 5.6K bytes
    - Viewed (0)
  2. docs/distributed/DESIGN.md

    are pariticipating in any erasure set. For example if you have 2 nodes with 180 drives then GCD is 15 but this would lead to uneven distribution, one of the nodes would participate more drives. To avoid this the affinity is given towards nodes which leads to next best GCD factor of 12 which provides uniform distribution.
    
    - In this algorithm, we also make sure that we spread the drives out evenly. MinIO server expands ellipses passed as arguments. Here is a sample expansion to demonstrate the...
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Tue Aug 15 23:04:20 GMT 2023
    - 8K bytes
    - Viewed (0)
  3. CREDITS

    network, you should also make sure that it provides a way for users to
    get its source.  For example, if your program is a web application, its
    interface could display a "Source" link that leads users to an archive
    of the code.  There are many ways you could offer source, and different
    solutions will be better for different programs; see section 13 for the
    specific requirements.
    
    Plain Text
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Fri Apr 26 06:31:35 GMT 2024
    - 1.6M bytes
    - Viewed (0)
Back to top