It is contending with sql.rows.awaitDone().
My guess is that when you close rows it has to wait for db acknowledgement -
that this is a false positive based on wall time and not cpu time - that the
mutex is waiting for the cleanup operation to complete.
> On Dec 13, 2023, at 1:25 PM, Joshua
The Go blog does indeed say this.
> The go tool no longer relies on pre-compiled standard library package
archives in the $GOROOT/pkg directory, and they are no longer shipped
with the distribution, resulting in smaller downloads. Instead, packages
in the standard library are built as needed
IIRC the stdlib isn't delivered precompiled anymore since 1.20. You should
make sure to have layer caching in place in case you want to tune your
pipelines. You can do a "go build std" IIRC.
On Wednesday, December 13, 2023 at 4:40:21 PM UTC+1 Lib Martinito wrote:
>
> [image: Screenshot
hi everyone
I am a newcomer of gollvm. And I spend some time on investigating about how
gollvm works.
When I read the code of llvm, I found something wired.
Why gollvm place llvm.statpoint in pad basicblock? Can we place the
llvm.statpoint on the normal basicblok?
Thanks in advance
David
I believe the intention is that you shouldn't format this, but make `err`
an `Attr`. i.e. the philosophy behind structured logging is specifically,
not to do formatting, as it produces unstructured data. Whether I'm
personally convinced by that philosophy is another question, but I think
that's
