Michał Matczuk 399cf18013 s3: use single memory pool ...

Previously we had a map of pools for different chunk sizes.
In practice the mapping is not very useful and requires a lock.
Pools of size other that ChunkSize can only happen when we have a huge file (over 10k * ChunkSize).
We need to have a bunch of identically sized huge files.
In such case most likely ChunkSize should be increased.

The mapping and its lock is replaced with a single initialised pool for ChunkSize, in other cases pool is allocated and freed on per file basis.

2020-04-11 16:34:05 +01:00

..

s3_test.go

s3: fix SetModTime on GLACIER/ARCHIVE objects and implement set/get tier

2019-09-14 09:18:55 +01:00

s3.go

s3: use single memory pool

2020-04-11 16:34:05 +01:00

v2sign.go

s3: fix v2 signer on files with spaces - fixes #2438

2018-10-14 00:10:29 +01:00