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.

Reply via email to