We will explore what it means to run @duckdb (an in-process analytical database) inside an @msftorleans application. An embedded, CPU-crunching database inside a highly concurrent actor runtime...should be fun :)
Happening TODAY at 9AM PT...
On .NET Live - DuckDB & Orleans: When Fake Asynchrony Starves Your App!
Learn the impact of using DuckDB within Microsoft Orleans grains, and how synchronous calls can cause scheduler starvation and reduced throughput.
🎥 ➡️ https://t.co/ScaTros6YM
Had the pleasure to be a guest on the NET Live Show! Myself & @reubenbond did a deep dive into the recent advancements for Placement & Balancing in @msftorleans@dotnet
https://t.co/Sq6fgNEVlB
Blogged: "Just how does a grain migrate?"
A deep dive into how the Orleans grain migration process works.
https://t.co/1z2Qxs9a8r
@msftorleans@dotnet#aspnetcore
@Aaronontheweb Interesting!!! I thought that was meant to be like that from the begining, essentially to fabor fire-and-forget style. Seems its more like a relict of old times.
@Aaronontheweb That failure may not arrive either. But i see the point/flow, i guess unless the state and reminder scheduling are stored atomically, such guarantees can not be made.
@Aaronontheweb I dont know what PipeTo(self) means but i would assume the (dotnet) task is put on the (actor) scheduler i.e. kind of "go back in the queue". If not, sorry i am naive about this.