Ledjon Behluli

I see myself as a specialist, who specializes in the big picture.

[Ledjon Behluli @BehluliLedjon]

Here is something I have been working on: Memory-aware Activation Rebalancing for @msftorleans / @dotnet

https://t.co/GcYMibgXGl

[Ledjon Behluli @BehluliLedjon]

@konradkokosa Super nice, congrats!

[Ledjon Behluli @BehluliLedjon]

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 :)

[.NET @dotnet]

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

[Joran Dirk Greef @jorandirkgreef]

(The same is true for performance)

[Ledjon Behluli @BehluliLedjon]

@reubenbond As many as there are [plug your number]-level inheritance hierarchies out there 😅

[Ledjon Behluli @BehluliLedjon]

@KooKiz @guardivelasquez Its typical for EF Core properties, but i'd argue applyinh [AllowNull] on the property is better.

[Ledjon Behluli @BehluliLedjon]

@dodyg Let me know if it was informative

[Ed Andersen @edandersen]

Microsoft Orleans is still incredible

[Ledjon Behluli @BehluliLedjon]

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

[Ledjon Behluli @BehluliLedjon]

@yevhen Last one blew my mind

[Ledjon Behluli @BehluliLedjon]

@dodyg Nice summary 😅

[Ledjon Behluli @BehluliLedjon]

@condef5 @msftorleans @dotnet Appriciated!

[Ledjon Behluli @BehluliLedjon]

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

[Ledjon Behluli @BehluliLedjon]

https://t.co/j5Gxzr2MwH

[dodyg @dodyg]

@TigerBeetleDB has a fantastic support for .NET. Use them in your business stack. https://t.co/rye5XWEYw9

[dodyg @dodyg]

Microsoft Orleans 9.20 with its Log-structured Grain Storage is fantastic https://t.co/TYklmJblps

[Ledjon Behluli @BehluliLedjon]

@Aaronontheweb Ah escaping the scheduler. Makes sense, thanks for the infos 🙂

[Ledjon Behluli @BehluliLedjon]

@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.

[Ledjon Behluli @BehluliLedjon]

@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.

[Ledjon Behluli @BehluliLedjon]

@Aaronontheweb Sorry for dragging on this but i am kind of (mis)using this thread to learn about akka without learning about akka 😅

[Ledjon Behluli @BehluliLedjon]

@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.