> In reality, on a standard linux system with overcommit enabled, stack pages are only consumed as they're written to - the rest is just virtual.
1. Once stack memory is committed, it is never uncommitted, and creating a new thread is relatively expensive.
2. Committing virtual memory is done at a page granularity.
These make threads far too costly to serve as a construct for any single concurrent task.