Tim Peters wrote:
>
> [Aaron Watters]
> > ...
> > I guess the question of interest is why are threads insufficient? I
> > guess they have system limitations on the number of threads or other
> > limitations that wouldn't be a problem with continuations?
>
> Sam is mucking with thousands of simultaneous I/O-bound socket connections,
> and makes a good case that threads simply don't fly here (each one consumes
> a stack, kernel resources, etc). It's unclear (to me) that thousands of
> continuations would be *much* better, though, by the time Christian gets
> done making thousands of copies of the Python stack chain.
Well, what he needs here are coroutines and just a single frame
object for every minithread (I think this is a "fiber"?).
If these fibers later do deep function calls before they switch,
there will of course be more frames then.
--
Christian Tismer :^) <mailto:tismer at appliedbiometrics.com>
Applied Biometrics GmbH : Have a break! Take a ride on Python's
Kaiserin-Augusta-Allee 101 : *Starship* http://starship.python.net
10553 Berlin : PGP key -> http://wwwkeys.pgp.net
PGP Fingerprint E182 71C7 1A9D 66E9 9D15 D3CC D4D7 93E2 1FAE F6DF
we're tired of banana software - shipped green, ripens at home
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4