g channel, but not many that are
faster than 10.2 nanoseconds.
From: <golang-nuts@googlegroups.com> on behalf of <vyasgiridha...@gmail.com>
Date: Monday, November 14, 2016 at 6:23 AM
To: golang-nuts <golang-nuts@googlegroups.com>
Cc: <vyasgiridha...@gmail.com>
Subject: Re: [go
Why would a select statement take up most of the execution time?
Is there another way to implement a non blocking channel?
On Monday, November 14, 2016 at 6:01:24 PM UTC+5:30, Michael Jones wrote:
>
> This is funny in the sense that my programs are great at stressing the CPU
> even though I
Why would a select statement take up most of the execution time?
Is there another way to implement a non blocking channel?
On Monday, November 14, 2016 at 6:01:24 PM UTC+5:30, Michael Jones wrote:
>
> This is funny in the sense that my programs are great at stressing the CPU
> even though I
This is funny in the sense that my programs are great at stressing the CPU even
though I don’t want to! :-)
I looked at your hogcpu() function and saw an issue: you busy loop repeats a
select statement and a square root. Almost any simple implementation of this
will spend all of its time
