Nick Craig-Wood 2ed0c688f6 pikpak: use pooled memory for the gcid hash buffer and spool unknown-size uploads to disk ...

When the source can't be re-opened, the whole input is read once to
compute its gcid before upload and held back for the upload proper. For
inputs at or below --pikpak-hash-memory-limit this used a bytes.Buffer,
a fresh heap allocation of up to the limit (and more while growing) per
file.

Hold the data in a buffer from the global memory pool instead so the
pages are reused and released on cleanup.

Inputs of unknown size were also always held in memory regardless of
their length, as only sizes above the limit chose the temp file.

Spool unknown sizes to the temp file so a large stream can't exhaust
memory.

2026-09-01 14:21:52 +01:00

..

api

build: modernize Go code with go fix for go1.25

2026-02-18 12:11:52 +00:00

helper_internal_test.go

pikpak: use pooled memory for the gcid hash buffer and spool unknown-size uploads to disk

2026-09-01 14:21:52 +01:00

helper.go

pikpak: use pooled memory for the gcid hash buffer and spool unknown-size uploads to disk

2026-09-01 14:21:52 +01:00

multipart.go

pikpak: share upload chunk buffers with the global memory pool

2026-09-01 14:21:52 +01:00

pikpak_test.go

pikpak: rewrite upload to bypass AWS S3 manager - fixes #8629

2025-07-04 11:25:12 +09:00

pikpak.go

pikpak: use pooled memory for the gcid hash buffer and spool unknown-size uploads to disk

2026-09-01 14:21:52 +01:00