mirror of
https://github.com/etcd-io/etcd.git
synced 2024-09-27 06:25:44 +00:00
*: docs and code %s%maximal%maximum%g
maximum is a more common word, use it instead
This commit is contained in:
parent
462baedcd4
commit
740187f199
@ -212,7 +212,7 @@ If timeout happens several times continuously, administrators should check statu
|
||||
|
||||
### Best Practices
|
||||
|
||||
#### Maximal OS threads
|
||||
#### Maximum OS threads
|
||||
|
||||
By default, etcd uses the default configuration of the Go 1.4 runtime, which means that at most one operating system thread will be used to execute code simultaneously. (Note that this default behavior [may change in Go 1.5](https://docs.google.com/document/d/1At2Ls5_fhJQ59kDK2DFVhFu3g5mATSXqqV5QrxinasI/edit)).
|
||||
|
||||
|
@ -19,8 +19,8 @@ import (
|
||||
)
|
||||
|
||||
const (
|
||||
// DefaultMaxIdleConnsPerHost indicates the default maximal idle connections
|
||||
// maintained between proxy and each member. We set it to 128 to
|
||||
// DefaultMaxIdleConnsPerHost indicates the default maximum idle connection
|
||||
// count maintained between proxy and each member. We set it to 128 to
|
||||
// let proxy handle 128 concurrent requests in long term smoothly.
|
||||
// If the number of concurrent requests is bigger than this value,
|
||||
// proxy needs to create one new connection when handling each request in
|
||||
|
@ -52,7 +52,7 @@ func TestPipelineSend(t *testing.T) {
|
||||
}
|
||||
}
|
||||
|
||||
func TestPipelineExceedMaximalServing(t *testing.T) {
|
||||
func TestPipelineExceedMaximumServing(t *testing.T) {
|
||||
tr := newRoundTripperBlocker()
|
||||
picker := mustNewURLPicker(t, []string{"http://localhost:2380"})
|
||||
fs := &stats.FollowerStats{}
|
||||
|
Loading…
x
Reference in New Issue
Block a user