Miloslav Trmač 8d76363085 Avoid a 32 kB file allocation on every bitBucketFilePutter.Put ... io.Copy usually allocates a 32kB buffer, and due to the large number of files processed by tar-split, this shows up in Go profiles as a very large alloc_space total. It doesn't seem to actually be a measurable problem in any way, but we can allocate the buffer only once per tar-split creation, at no additional cost to existing allocations, so let's do so, and remove the distraction. Signed-off-by: Miloslav Trmač <mitr@redhat.com>		2021-08-21 03:24:39 +02:00
..
asm	tar: asm: add an excess padding test case	2017-11-08 02:35:01 +11:00
storage	Avoid a 32 kB file allocation on every bitBucketFilePutter.Put	2021-08-21 03:24:39 +02:00