22-Sep-2014 01:45, Ola Fosheim Grostad пишет:
On Sunday, 21 September 2014 at 17:52:42 UTC, Dmitry Olshansky wrote:
to use non-atomic ref-counting and have far less cache pollution (the
set of fibers to switch over is consistent).
Caches are not a big deal when you wait for io.
Go also check fiber
stack size... But maybe Go should not be considered a target.
??? Just reserve more space. Even Go dropped segmented stack.
What Go has to do with this discussion at all BTW?
Because that is what you are competing with in the webspace.
E-hm Go is hardly the top dog in the web space. Java and JVM crowd like
(Scala etc.) are apparently very sexy (and performant) in the web space.
They try to sell it as if it was all the rage though.
IMO Go is hardly an interesting opponent to compete against. In pretty
much any use case I see Go is somewhere down to 4-th+ place to look at.
Go checks and extends stacks.
Since 1.2 or 1.3 i.e. relatively new stuff.
--
Dmitry Olshansky
