@wycats If you mean something as lightweight as an Erlang process, I’d answer your question with “none”
-
-
-
@stilkov when do you think the overhead starts becoming a problem? Seems like for general purpose APIs it's rarely an issue.
End of conversation
New conversation -
-
-
@wycats If async can improve max connections/CPU, then there's the value. Seems like an empirical question dependent on the platform. -
@wycats e.g. how many of these green threads can Rust support at once? -
@jamesmacaulay if the answer is "not enough" Rust should improve the situation. Forking the programming model has a high cost.
End of conversation
New conversation -
-
-
@wycats To me, “green thread” seems to imply something just as heavy as an OS thread, just with faster switching and no true parallelismThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wycats Scheduler implementations (both native and green) are made for the general case and may require more overhead than you can allow.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.