K on Nostr: goos: linux goarch: amd64 pkg: github.com/nbd-wtf/go-nostr cpu: 12th Gen Intel(R) ...
goos: linux
goarch: amd64
pkg: github.com/nbd-wtf/go-nostr
cpu: 12th Gen Intel(R) Core(TM) i3-12100F
BenchmarkParseMessage
BenchmarkParseMessage/golang
BenchmarkParseMessage/golang-8 162 6665196 ns/op
BenchmarkParseMessage/simdjson
BenchmarkParseMessage/simdjson-8 28 43713545 ns/op
PASS
ok github.com/nbd-wtf/go-nostr 3.138s
i was not aware of simdjson on go...
but it seems its for 2 years ago. forking it? you do it or i can go for it?
also, these stuff like simdjson and linsecp245k1 in golang has a lot of overhead, what is your opinion?
goarch: amd64
pkg: github.com/nbd-wtf/go-nostr
cpu: 12th Gen Intel(R) Core(TM) i3-12100F
BenchmarkParseMessage
BenchmarkParseMessage/golang
BenchmarkParseMessage/golang-8 162 6665196 ns/op
BenchmarkParseMessage/simdjson
BenchmarkParseMessage/simdjson-8 28 43713545 ns/op
PASS
ok github.com/nbd-wtf/go-nostr 3.138s
i was not aware of simdjson on go...
but it seems its for 2 years ago. forking it? you do it or i can go for it?
also, these stuff like simdjson and linsecp245k1 in golang has a lot of overhead, what is your opinion?