Thank you for including examples and patterns in your talk! So many of these talks discuss the theory, but don't offer a simple practical example to help relate the principle to the practice.
There's a lot of great information in here. Nicely done! With some of the tips provided, it seemed to me like Pamela described the Actor model using multiprocessing. Wikipedia has a very dry presentation of that design style at en.wikipedia.org/wiki/Actor_model, but, the short version is that using messages and queues/mailboxes is a way to share state between processes in a way that will parallelize well.
Conferences are a million times better than "nuggets". Instead of cut-down tailored unrelate-able tech notes you get to witness first hand the other person's personal experience.
Using threads vs multiprocessing... or queues vs pipes... or when to use .join have always been a source of confusion for me! I understand that multiprocessing's Queue will .get() one element at a time... But suppose you're writing several bytes worth of data in a queue (in the form of a tuple)... what happens if try to read from the queue, while the write hasn't finished the tuple? Does it block until the tuple is finished, does it return empty, or does it return the partial bytes in the tuple?
Thank you for including examples and patterns in your talk!
So many of these talks discuss the theory, but don't offer a simple practical example to help relate the principle to the practice.
Tips begin at 9:48
Very valuable knowledge! Thanks Pamela!
Thank you for this Pamela! This is a lot clearer than most examples and talks I've seen on the subject.
You're welcome!
There's a lot of great information in here. Nicely done!
With some of the tips provided, it seemed to me like Pamela described the Actor model using multiprocessing. Wikipedia has a very dry presentation of that design style at en.wikipedia.org/wiki/Actor_model, but, the short version is that using messages and queues/mailboxes is a way to share state between processes in a way that will parallelize well.
Thanks, Pamela!
Conferences are a million times better than "nuggets". Instead of cut-down tailored unrelate-able tech notes you get to witness first hand the other person's personal experience.
Using threads vs multiprocessing... or queues vs pipes... or when to use .join have always been a source of confusion for me!
I understand that multiprocessing's Queue will .get() one element at a time...
But suppose you're writing several bytes worth of data in a queue (in the form of a tuple)... what happens if try to read from the queue, while the write hasn't finished the tuple? Does it block until the tuple is finished, does it return empty, or does it return the partial bytes in the tuple?
Dont share, pass messages, Just like Golang
This Pamela had a voice mutation?
She was declared and malloc'ed as one type and type casted into another much much later.
@@doc0core 🤣