-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[draft/wip] Adding (initial) fortio.org/log entry #1317
Open
ldemailly
wants to merge
5
commits into
uber-go:master
Choose a base branch
from
ldemailly:fortio_bench
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
130de6e
Adding (initial) fortio.org/log entry
ldemailly 8788569
Use numbers whose alloc isn't optimized away by go
ldemailly b113ea6
rerun and small fix to slog in case it starts doing like log. io.Disc…
ldemailly 1e075db
using release version of fortio.org/log
ldemailly 812df0a
remove dup replace go.uber.org/zap => ../
ldemailly File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,79 @@ | ||
// Copyright (c) 2016 Uber Technologies, Inc. | ||
// | ||
// Permission is hereby granted, free of charge, to any person obtaining a copy | ||
// of this software and associated documentation files (the "Software"), to deal | ||
// in the Software without restriction, including without limitation the rights | ||
// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | ||
// copies of the Software, and to permit persons to whom the Software is | ||
// furnished to do so, subject to the following conditions: | ||
// | ||
// The above copyright notice and this permission notice shall be included in | ||
// all copies or substantial portions of the Software. | ||
// | ||
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | ||
// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | ||
// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE | ||
// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER | ||
// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, | ||
// OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN | ||
// THE SOFTWARE. | ||
|
||
package benchmarks | ||
|
||
import ( | ||
"io" | ||
|
||
"fortio.org/log" | ||
) | ||
|
||
type shmLogger struct { | ||
fields []log.KeyVal | ||
} | ||
|
||
var fLog = &shmLogger{} | ||
|
||
func (l *shmLogger) Infof(msg string, fields ...interface{}) { | ||
log.Infof(msg, fields...) | ||
} | ||
|
||
func (l *shmLogger) InfoS(msg string, fields ...log.KeyVal) { | ||
log.S(log.Info, msg, fields...) | ||
} | ||
|
||
func (l *shmLogger) InfoContext(msg string) { | ||
log.S(log.Info, msg, l.fields...) | ||
} | ||
|
||
func newFortiolog(fields ...log.KeyVal) *shmLogger { | ||
log.Config = log.DefaultConfig() | ||
log.Config.LogFileAndLine = false // file/line extraction implies bad perf | ||
log.Config.JSON = true // structured logging comparison | ||
log.Config.GoroutineID = false // other loggers don't have that | ||
log.SetOutput(io.Discard) | ||
log.Color = false // should already be but just in case | ||
fLog.fields = fields | ||
log.SetLogLevel(log.Info) | ||
return fLog | ||
} | ||
|
||
func newDisabledFortiolog(fields ...log.KeyVal) *shmLogger { | ||
logger := newFortiolog() | ||
log.SetLogLevel(log.Error) | ||
logger.fields = fields | ||
return logger | ||
} | ||
|
||
func fakeFortiologFields() []log.KeyVal { | ||
return []log.KeyVal{ | ||
log.Attr("int", _tenInts[0]), | ||
log.Attr("ints", _tenInts), | ||
log.Str("string", _tenStrings[0]), | ||
log.Attr("strings", _tenStrings), | ||
log.Attr("time", _tenTimes[0]), | ||
log.Attr("times", _tenTimes), | ||
log.Attr("user1", _oneUser), | ||
log.Attr("user2", _oneUser), | ||
log.Attr("users", _tenUsers), | ||
log.Attr("error", errExample), | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair point. If you're still experimenting with this PR, you can probably get this specific change merged as a separate PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks btw, how / on which machine do you run
make updatereadme
as the absolute (and seemingly even some times the relative numbers) depends on the hw/arch/os it's being ran on ?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think original runs were on Intel Macbook Pros, and since then on Apple Silicon Macbook Pros.
Absolute numbers are less important than the relative performance, so as long as the numbers are consistent and the benchmarks were all run on the same machine, it should be good to check-in.