minio

History

Harshavardhana 0104af6bcc delayed locks until we have started reading the body (#10474 ) This is to ensure that Go contexts work properly, after some interesting experiments I found that Go net/http doesn't cancel the context when Body is non-zero and hasn't been read till EOF. The following gist explains this, this can lead to pile up of go-routines on the server which will never be canceled and will die at a really later point in time, which can simply overwhelm the server. https://gist.github.com/harshavardhana/c51dcfd055780eaeb71db54f9c589150 To avoid this refactor the locking such that we take locks after we have started reading from the body and only take locks when needed. Also, remove contextReader as it's not useful, doesn't work as expected context is not canceled until the body reaches EOF so there is no point in wrapping it with context and putting a `select {` on it which can unnecessarily increase the CPU overhead. We will still use the context to cancel the lockers etc. Additional simplification in the locker code to avoid timers as re-using them is a complicated ordeal avoid them in the hot path, since locking is very common this may avoid lots of allocations.		4 years ago
..
azure	delayed locks until we have started reading the body (#10474 )	4 years ago
gcs	delayed locks until we have started reading the body (#10474 )	4 years ago
hdfs	delayed locks until we have started reading the body (#10474 )	4 years ago
nas	Use constants for gateway names to avoid bugs caused by spelling. (#10355 )	4 years ago
s3	delayed locks until we have started reading the body (#10474 )	4 years ago
gateway.go	…