-
Notifications
You must be signed in to change notification settings - Fork 69
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore(dev-deps): bump ts, ts-patch (#1103)
- Loading branch information
Showing
2 changed files
with
10 additions
and
15 deletions.
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
69178fb
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.
Logger Benchmarks - ubuntu-latest
Child logger creation
476941
ops/sec (±0.62%
)461557
ops/sec (±1.19%
)0.97
Logging a string on root logger
814969
ops/sec (±7.20%
)785793
ops/sec (±8.34%
)0.96
Logging an object on root logger
703782
ops/sec (±4.95%
)549003
ops/sec (±8.10%
)0.78
Logging an object with a message on root logger
22911
ops/sec (±184.71%
)7886
ops/sec (±203.05%
)0.34
Logging an object with a redacted prop on root logger
457484
ops/sec (±8.32%
)447456
ops/sec (±8.97%
)0.98
Logging a nested 3-level object on root logger
24505
ops/sec (±183.98%
)359027
ops/sec (±10.09%
)14.65
This comment was automatically generated by workflow using github-action-benchmark.
69178fb
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.
Possible performance regression was detected for benchmark 'Logger Benchmarks - ubuntu-latest'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold
2
.Logging a nested 3-level object on root logger
24505
ops/sec (±183.98%
)359027
ops/sec (±10.09%
)14.65
This comment was automatically generated by workflow using github-action-benchmark.
69178fb
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.
Logger Benchmarks - windows-latest
Child logger creation
348829
ops/sec (±0.29%
)333802
ops/sec (±0.85%
)0.96
Logging a string on root logger
844579
ops/sec (±7.45%
)742261
ops/sec (±5.41%
)0.88
Logging an object on root logger
609856
ops/sec (±8.58%
)604551
ops/sec (±5.42%
)0.99
Logging an object with a message on root logger
3155
ops/sec (±228.31%
)7988
ops/sec (±200.08%
)2.53
Logging an object with a redacted prop on root logger
403616
ops/sec (±16.18%
)474325
ops/sec (±7.47%
)1.18
Logging a nested 3-level object on root logger
315711
ops/sec (±5.39%
)318847
ops/sec (±5.26%
)1.01
This comment was automatically generated by workflow using github-action-benchmark.
69178fb
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.
Possible performance regression was detected for benchmark 'Logger Benchmarks - windows-latest'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold
2
.Logging an object with a message on root logger
3155
ops/sec (±228.31%
)7988
ops/sec (±200.08%
)2.53
This comment was automatically generated by workflow using github-action-benchmark.