I don't know much about the internal implementation of golang, sorry. I was a c programmer and I tried to implement the original logic (olap database) by using routine as a thread replacement. But I found that I would encounter bottlenecks, and I don't know how to solve them. Maybe I should study the implementation of routine before I can write the right code.
在2021年2月2日星期二 UTC+8 下午12:21:44<ren...@ix.netcom.com> 写道： > You wrote “I found that cache misses from routines switching is also a > headache”. > > They would not be switching if they are cpu bound and there are less of > than number of cpus. Remember too that you need some % of the cpus to > execute the runtime GC code and other housekeeping. > > > On Feb 1, 2021, at 10:04 PM, 颜文泽 <nnsm...@gmail.com> wrote: > > > > I found that cache misses from routines switching is also a headache > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/35bccad0-64a9-4796-bc3f-a9cdb8c82961n%40googlegroups.com.
