https://markpelf.com ,NET Blog by Mark Pelf Fri, 05 Jan 2024 08:58:29 +0000 hourly 1 https://markpelf.com/1028/discussing-alternative-memory-management-strategy-for-net/#comment-64 Fri, 05 Jan 2024 08:58:29 +0000 https://www.markpelf.com/?p=1028#comment-64 Dear Mark, all you mentioned in your article makes much sense because that`s pretty much what I was thinking about last time when writing so-called low latency applications. Especially when you want to write C++ style memory management apps with manual object creation and deletion, but forced to use C# because of other restrictions. My I was thinking that definitely C# with its GC is not created for for extremely low latency apps, but we try to find a workaround, even if it`s not beautiful. o I thought, as one of possible solutions, why don`t we create objects with AllocHGlobal or AllocCoTaskMem and delete the objects manually inside unsafe blocks. I understand that this way we will have to write pretty much all code in unsafe blocks and that we cant eliminate GC suspending threads at all when collecting garbage, but we can minimize the number of objects allocated in the managed heap, so that GC collection will occur much less frequently. Most of our objects we will allocate and delete manually what will free GC from doing most of work. But in general, I agree with your GDC suggestion. That would be great if this sort of C++ style memory management with virtual distructor would be implemented, so that devs can choose which mode to use.

]]> https://markpelf.com/1028/discussing-alternative-memory-management-strategy-for-net/#comment-55 Sat, 04 Mar 2023 19:14:34 +0000 https://www.markpelf.com/?p=1028#comment-55 Actually I was googling for the same topic, if you look at carbon language,. You will find something like heap.new , heap.delete
I wonder if there could be a similar in dotnet

]]>