Skip to content

v3: design API to avoid allocations in responses #493

@oleg-jukovec

Description

@oleg-jukovec

The memory profile for a benchmark could be viewed as follows:

$ go test -v . -bench BenchmarkSync_naive_with_custom_type -benchmem -run foobar -memprofile mem.out
$ go tool pprof -http ":8080" mem.out

As you can see, several allocations are related to a response:

Image

Our task is to design API of responses/futures to avoid these allocations.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions