Re: [go-nuts] CPU-intensive Go applications

2017-03-03 Thread Sebastien Binet
dharani, On Sat, Mar 4, 2017 at 12:03 AM, Tharaneedharan Vilwanathan < vdhar...@gmail.com> wrote: > Hi, > > Ian, thanks for the quick response and useful info. I will give it a try. > > Request you all to share more thoughts. > here is the document that sparked the discussion Ian was alluding to

Re: [go-nuts] CPU-intensive Go applications

2017-03-03 Thread Tharaneedharan Vilwanathan
Hi, Ian, thanks for the quick response and useful info. I will give it a try. Request you all to share more thoughts. Thanks dharani On Fri, Mar 3, 2017 at 2:54 PM, Ian Lance Taylor wrote: > On Fri, Mar 3, 2017 at 2:21 PM, Tharaneedharan Vilwanathan > wrote: > > > > I am working on some cpu

Re: [go-nuts] CPU-intensive Go applications

2017-03-03 Thread Ian Lance Taylor
On Fri, Mar 3, 2017 at 2:21 PM, Tharaneedharan Vilwanathan wrote: > > I am working on some cpu-intensive Go applications. > > I want to avoid the scheduler from moving the tasks to various cores. I am > trying to pin the code to specific CPU cores and see if I can get better, > predictable perform

[go-nuts] CPU-intensive Go applications

2017-03-03 Thread Tharaneedharan Vilwanathan
Hi All, I am working on some cpu-intensive Go applications. I want to avoid the scheduler from moving the tasks to various cores. I am trying to pin the code to specific CPU cores and see if I can get better, predictable performance. Is there any info available that documents various techniques,