[concurrency-interest] Default Stack Size on 64-bit JVMs

Henrik Johansson dahankzter at gmail.com
Thu Dec 3 01:54:07 EST 2015


However Go does it nicely and the concept of small growable stacks is in
itself very appealing. Wouldn't it help many use cases like parallel
streams of small computational units as well not just recursion?

On Thu, Dec 3, 2015, 05:53 Martin Buchholz <martinrb at google.com> wrote:

> On Wed, Dec 2, 2015 at 4:45 PM, Vitaly Davidovich <vitalyd at gmail.com>
> wrote:
> >> and of course start working on the difficult task of being able to move
> >> the stack so that if you run out of room, simply realloc and move
> elsewhere,
> >> like the competition is doing.
> >
> >
> > IIRC, Rust moved away from segmented stacks.  Go I guess still uses them?
> > It's likely a performance loss for ordinary threading, but would be
> required
> > for coroutine/fiber support (like Go has).
>
> You're right!  Wishful thinking.  Go has moved away from segmented
> stacks, but tries to resize them as needed.  They need to keep track
> of every pointer that could ever point inside a stack.
>
> This certainly weakens my case.
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20151203/27e3007b/attachment.html>


More information about the Concurrency-interest mailing list