Add pprof to the k6 itself #20
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
#26 Add explicit reiteration delay to object selector}
TrueCloudLab/xk6-frostfs
Reference: TrueCloudLab/xk6-frostfs#20
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
After #16 I was thinking whether we need to profile k6 itself.
I think the answer is yes, at least we could test some hypotheses.
The smaller object we PUT the bigger relative overhead could be.
PProf allows us not to guess, but make it obvious.
Closed via #56.