You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 20, 2022. It is now read-only.
When using go-osmpbf (https://github.com/qedus/osmpbf), fmp.Printf("number of goroutines for decoding = %d", runtime.GOMAXPROCS(-1))
would print helpful information. I suspect it to be one.
Note that it is used in the code as follows: err = d.Start(runtime.GOMAXPROCS(-1)) // use several goroutines for faster decoding
The text was updated successfully, but these errors were encountered:
hey @kkdd this is being set to -1 like you said, which is why it's the fastest from the test results, what makes you think it's still bound to a single core?
I finally understand Goroutine's threads as follows:
ncpu := 2 // specifying the number of CPU which Golang uses
runtime.GOMAXPROCS(ncpu) // Note that ncpu == runtime.GOMAXPROCS(-1)
err = d.Start(ncpu) // specifying the number of Goroutine's threads
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using go-osmpbf (https://github.com/qedus/osmpbf),
fmp.Printf("number of goroutines for decoding = %d", runtime.GOMAXPROCS(-1))
would print helpful information. I suspect it to be one.
Note that it is used in the code as follows:
err = d.Start(runtime.GOMAXPROCS(-1)) // use several goroutines for faster decoding
The text was updated successfully, but these errors were encountered: