Go is a shared memory system. Your challenge would be to understand a pointer that came to you from a different machine (i.e., remotely, the R in RPC).
On Fri, Jan 3, 2020 at 2:31 PM <dola...@gmail.com> wrote: > Hi all and Happy New Year, > > I was daydreaming the other day and I was wondering if it was possible to > create some alternate runtime package. > The point would be to have the scheduler schedule goroutine not only on > different CPU, but also on different CPU on different machines. > The system would be a binary that you could run as the scheduler or as a > worker, and the scheduler would distribute among workers via some RPC. Of > course, it would take cache optimisation to schedule it on the correct > machine so they could share the same CPU when needed. > Is it a stupid idea? A very difficult one? A naive approach that would > just have networking bandwidth and latency issues? > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/5a05e457-4d9d-45b2-9822-d1accb48d7af%40googlegroups.com > <https://groups.google.com/d/msgid/golang-nuts/5a05e457-4d9d-45b2-9822-d1accb48d7af%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- *Michael T. jonesmichael.jo...@gmail.com <michael.jo...@gmail.com>* -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CALoEmQw06TmJO5qET%3DdfjfTFQwNqZwjUhxv57q%3DcjRrch1LDrA%40mail.gmail.com.
