6 ms·
I dont think libdill supports multiple CPUs, which is really hard to get right
by latenightcoding 6y ago
I dont think libdill supports multiple CPUs, which is really hard to get right
- armitron 6y agoWell it does not allow coroutines to migrate to different OS threads and handles to be shared across OS threads, but that does not mean it doesn't support multiple CPUs. It's more correct to say that it doesn't come with that support out of the box, but it certainly does allow for it and nudges you towards a specific direction (no shared mutable state).
- throwaway17_17 6y agoThat has been my experience using the library, I have found that it really encourages, by means of making it the most expedient option to have write once data structures. My use case is certainly not the common one though, so others may have different experiences.
- ioquatix 6y agoYou run multiple instances, one per CPU core.
- latenightcoding 6y agothere is a huge difference between running an instance per CPU and letting a smart scheduler orchestrate things for you.
- ignoramous 6y agoReminds me of this epic discussion between KirinDave, Ryan Dahl, and Aphyr: https://news.ycombinator.com/item?id=4306241 https://news.ycombinator.com/item?id=4306241
- zekrioca 6y agoParent my have a StackOverFlow CV.. :)