Calin M
Calin M
Go lint fails, please change the commit message with conventions used in Bee.
LevelDB Benchmarks: ``` cpu: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz BenchmarkStore/WriteSequential-12 766509 1562 ns/op 1605 B/op 8 allocs/op BenchmarkStore/WriteRandom/parallelism-1-12 668485 4347 ns/op 3067 B/op 9 allocs/op BenchmarkStore/WriteRandom/parallelism-2-12 320804 5577 ns/op...
Pebble DB Benchmarks: ``` cpu: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz BenchmarkStore/WriteSequential-12 1016307 1253 ns/op 972 B/op 5 allocs/op BenchmarkStore/WriteRandom/parallelism-1-12 744579 3312 ns/op 2584 B/op 5 allocs/op BenchmarkStore/WriteRandom/parallelism-2-12 434683 3721...
Closing this to focus on improving LevelDB performance through configuration tuning.
> Just to mention another tool for the job https://opentelemetry.io/. Since we are using the OpenTracing library that is an archived project we might switch to OpenTelemetry as they also...
Can you try reproduce it with the latest Bee? I can not reproduce it.
Please fix the linter error, check this out this for the commit message [commitlint](https://github.com/ethersphere/bee/blob/master/commitlint.config.js). Also you can checkout previous commit messages. you can use as message something like this `fix:...
LGTM , but needs more testing
Is there a way we can test this?
As I investigated this issue, it could be that upgrading `github.com/libp2p/go-libp2p` to `v0.42.0` , might have fixed the issues we had with `github.com/libp2p/go-libp2p v0.33.2`