March 18, 2014 Re: Remember that Go vs D MQTT thing and how we wondered about dmd vs gdc? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Sönke Ludwig | Am Wed, 12 Mar 2014 10:41:11 +0100 schrieb Sönke Ludwig <sludwig+dforum@outerproduct.org>: > But since the memory pages of a fiber's stack are allocated lazily, at least on a 64-bit OS, where address space is not an issue, you can actually scale to very high numbers with a decent amount of RAM. This means for each fiber, you allocate e.g. 1 MiB virtual memory as a stack and let page faults allocate them from RAM on demand, right? -- Marco |
March 18, 2014 Re: Remember that Go vs D MQTT thing and how we wondered about dmd vs gdc? | ||||
---|---|---|---|---|
| ||||
Posted in reply to Marco Leise | Am 18.03.2014 03:15, schrieb Marco Leise:
> Am Wed, 12 Mar 2014 10:41:11 +0100
> schrieb Sönke Ludwig <sludwig+dforum@outerproduct.org>:
>
>> But since the memory pages of a fiber's stack are allocated lazily, at
>> least on a 64-bit OS, where address space is not an issue, you can
>> actually scale to very high numbers with a decent amount of RAM.
>
> This means for each fiber, you allocate e.g. 1 MiB virtual
> memory as a stack and let page faults allocate them from RAM
> on demand, right?
>
Exactly. Currently the stack size is set to only 64k to get a good trade-off on 32-bit systems, but I've been thinking about using a version(D_LP64) to increase this default for 64-bit.
|
Copyright © 1999-2021 by the D Language Foundation