What does allocs/op and B/op mean in go benchmark?
When I run my benchmarks with go test -v -bench=. -benchmem
, I see the following results.
f1 10000 120860 ns/op 2433 B/op 28 allocs/op
f2 10000 120288 ns/op 2288 B/op 26 allocs/op
Based on my understanding:
10000
is the number of iterationsfor i := 0; i < b.N; i++ {
.
XXX ns/op
is approximate time it took for one iteration to complete
But even after reading the docs, I can not find out what B/op
and allocs/op
mean.
My guess is that allocs/op has something to do with garbage collection and memory allocation (the less the better).
Can anyone give a nice explanation of the meaning of these values. Also it would be nice to know why do the go up and main steps to reduce them (I realize this is test specific, but may be there are some universal hints that work in many cases)
go benchmarking
add a comment |
When I run my benchmarks with go test -v -bench=. -benchmem
, I see the following results.
f1 10000 120860 ns/op 2433 B/op 28 allocs/op
f2 10000 120288 ns/op 2288 B/op 26 allocs/op
Based on my understanding:
10000
is the number of iterationsfor i := 0; i < b.N; i++ {
.
XXX ns/op
is approximate time it took for one iteration to complete
But even after reading the docs, I can not find out what B/op
and allocs/op
mean.
My guess is that allocs/op has something to do with garbage collection and memory allocation (the less the better).
Can anyone give a nice explanation of the meaning of these values. Also it would be nice to know why do the go up and main steps to reduce them (I realize this is test specific, but may be there are some universal hints that work in many cases)
go benchmarking
add a comment |
When I run my benchmarks with go test -v -bench=. -benchmem
, I see the following results.
f1 10000 120860 ns/op 2433 B/op 28 allocs/op
f2 10000 120288 ns/op 2288 B/op 26 allocs/op
Based on my understanding:
10000
is the number of iterationsfor i := 0; i < b.N; i++ {
.
XXX ns/op
is approximate time it took for one iteration to complete
But even after reading the docs, I can not find out what B/op
and allocs/op
mean.
My guess is that allocs/op has something to do with garbage collection and memory allocation (the less the better).
Can anyone give a nice explanation of the meaning of these values. Also it would be nice to know why do the go up and main steps to reduce them (I realize this is test specific, but may be there are some universal hints that work in many cases)
go benchmarking
When I run my benchmarks with go test -v -bench=. -benchmem
, I see the following results.
f1 10000 120860 ns/op 2433 B/op 28 allocs/op
f2 10000 120288 ns/op 2288 B/op 26 allocs/op
Based on my understanding:
10000
is the number of iterationsfor i := 0; i < b.N; i++ {
.
XXX ns/op
is approximate time it took for one iteration to complete
But even after reading the docs, I can not find out what B/op
and allocs/op
mean.
My guess is that allocs/op has something to do with garbage collection and memory allocation (the less the better).
Can anyone give a nice explanation of the meaning of these values. Also it would be nice to know why do the go up and main steps to reduce them (I realize this is test specific, but may be there are some universal hints that work in many cases)
go benchmarking
go benchmarking
asked Feb 23 '16 at 21:24
Salvador DaliSalvador Dali
113k81491580
113k81491580
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
allocs/op
means how many distinct memory allocations occurred per op (single iteration).
B/op
is how many bytes were allocated per op.
Is that B/op the allocations, made in stake frame or in heap? Or is it what the memory amount that GO GC has to clean?
– user3219492
Aug 4 '17 at 19:45
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f35588474%2fwhat-does-allocs-op-and-b-op-mean-in-go-benchmark%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
allocs/op
means how many distinct memory allocations occurred per op (single iteration).
B/op
is how many bytes were allocated per op.
Is that B/op the allocations, made in stake frame or in heap? Or is it what the memory amount that GO GC has to clean?
– user3219492
Aug 4 '17 at 19:45
add a comment |
allocs/op
means how many distinct memory allocations occurred per op (single iteration).
B/op
is how many bytes were allocated per op.
Is that B/op the allocations, made in stake frame or in heap? Or is it what the memory amount that GO GC has to clean?
– user3219492
Aug 4 '17 at 19:45
add a comment |
allocs/op
means how many distinct memory allocations occurred per op (single iteration).
B/op
is how many bytes were allocated per op.
allocs/op
means how many distinct memory allocations occurred per op (single iteration).
B/op
is how many bytes were allocated per op.
answered Feb 23 '16 at 21:36
Not_a_GolferNot_a_Golfer
29.4k28163
29.4k28163
Is that B/op the allocations, made in stake frame or in heap? Or is it what the memory amount that GO GC has to clean?
– user3219492
Aug 4 '17 at 19:45
add a comment |
Is that B/op the allocations, made in stake frame or in heap? Or is it what the memory amount that GO GC has to clean?
– user3219492
Aug 4 '17 at 19:45
Is that B/op the allocations, made in stake frame or in heap? Or is it what the memory amount that GO GC has to clean?
– user3219492
Aug 4 '17 at 19:45
Is that B/op the allocations, made in stake frame or in heap? Or is it what the memory amount that GO GC has to clean?
– user3219492
Aug 4 '17 at 19:45
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f35588474%2fwhat-does-allocs-op-and-b-op-mean-in-go-benchmark%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown