Just realized I now to use taskset to make sure all the goroutine run on
the same CPU
sudo taskset -c 7 ./sche -r 0.3s
and It's working now
On Thursday, September 26, 2024 at 11:49:53 AM UTC+8 Zhao Weng wrote:
> Hi gophers,
> I'm doing a research on how to prioritise some goroutines over other
Hi gophers,
I'm doing a research on how to prioritise some goroutines over others.So I
can allocate more CPU resource to more important part of the program.
I try to do it by calling runtime.LockOSThread to assign the goroutine
needs to be prioritise to a designated OS thread, and unix.SchedSetA
Hi everyone, I've recently been working on a new Qt Widgets binding for Go.
You can check it out here: https://github.com/mappu/miqt
Qt is a popular LGPL C++ framework that is mostly famous for Qt Widgets,
a traditional desktop GUI toolkit, crossplatform for Windows, macOS,
Linux, and mobile.
I don't believe this is contradictory. TL;DR: `error` is a (very) special
case, part of the language specification itself.
Long-form (my take):
The guidance in CodeReviewComments relate to interface types and any
implementation defined by a project.
The guidance in faq#nil_error relates to c
Sorry to revive this, but I'd like to add to conversation (without weighing
in on correctness of the nil check) that it appears the CodeReview comments
on interfaces ( https://go.dev/wiki/CodeReviewComments#interfaces ) and the
FAQ nil error https://go.dev/doc/faq#nil_error give mutually exclus
