Re: [go-nuts] The right way for golang binary to reduce iTLB cache miss

I can’t imagine the app has 34 mb of code in the hot path where this would matter - so I assume the application is partitioned with various Go routines doing a “type” of work. Which encounters a problem with the Go design. You can’t partition Go routines, and you can’t set cpu/core affinity for

Re: [go-nuts] The right way for golang binary to reduce iTLB cache miss

I have tried to disable the inline during compiling, but it results in no big difference. On Saturday, September 18, 2021 at 9:26:45 PM UTC+8 ren...@ix.netcom.com wrote: > I will add that over aggressive inlining can cause this - it explodes the > binary size. > > On Sep 18, 2021, at 7:37 AM,

Re: [go-nuts] The right way for golang binary to reduce iTLB cache miss

The problem is this application is a quite big Golang project. It has about 500, 000 lines of Golang codes and didn't even count these required 3-rd party libraries. On Sunday, September 19, 2021 at 8:47:44 AM UTC+8 rmfr wrote: > One of our Golang applications has a very huge binary size and th

Re: [go-nuts] The right way for golang binary to reduce iTLB cache miss

One of our Golang applications has a very huge binary size and the size of the .text segment itself in the elf is approximately *34MB*. The iTLB load miss reaches about *87%* of all iTLB cache hits. >> Is there any advice for big Golang applications to reduce the iTLB cache miss? Two solutions

Re: [go-nuts] The right way for golang binary to reduce iTLB cache miss

I will add that over aggressive inlining can cause this - it explodes the binary size. > On Sep 18, 2021, at 7:37 AM, Jesper Louis Andersen > wrote: > > On Fri, Sep 17, 2021 at 11:09 AM rmfr > wrote: > One of our Golang applications has a very huge binary si

Re: [go-nuts] The right way for golang binary to reduce iTLB cache miss

On Fri, Sep 17, 2021 at 11:09 AM rmfr wrote: > One of our Golang applications has a very huge binary size and the size of > the .text segment itself in the elf is approximately *34MB*. The iTLB > load miss reaches about *87%* of all iTLB cache hits. > > Is there any advice for big Golang applicat

[go-nuts] The right way for golang binary to reduce iTLB cache miss

One of our Golang applications has a very huge binary size and the size of the .text segment itself in the elf is approximately *34MB*. The iTLB load miss reaches about *87%* of all iTLB cache hits. Is there any advice for big Golang applications to reduce the iTLB cache miss? Two solutions com