Span, Memory i ReadOnlySequence stały się stałym elementem .NET i pojawiają się praktycznie wszędzie. Kiedy przeglądałem dokumentację tych struktur, zauważyłem, że to w jaki sposób mam je zamodelowane w głowie różni się od dokumentacji. Zapraszam do wizyty w świat niskopoziomowego spotkania z pamięcią i tego jak to rozumiemy. Zapraszam tym mocniej, jeżeli pojęć tych nie używasz codziennie, a chszesz je zrozumieć.
Sztuka programowania 1425 dni, 6 godzin, 34 minuty temu 228 źrodło rozwiń
This video will show you some of the performance and allocation problems that you might encounter when writing LINQ expressions and offer a couple of solutions on how to solve them. LINQ Links: ♦ https://github.com/NetFabric/LinqBenchmarks ♦ https://github.com/NetFabric/NetFabric.Hyperlinq
Sztuka programowania 1603 dni, 7 godzin, 32 minuty temu 57 źrodło rozwiń
So…after quite a serious thing which was writing Pro .NET Memory Management book, I’ve decided to experiment with a little pet project for having some more fun. I have quite a few very interesting ideas going on in my head. Yet, I needed to choose one! And that’s how an idea of OutOfMemory game prototype materialized!
Would be post-mortem finalization available thanks to phantom references useful in .NET? What is your opinion, especially based on your experience with the finalization of your use cases? Please, share your insights in comments!
Hi all! I am thrilled to announce that after more than two years of intensive book writing, it is finally available for preorder! Its about 800 pages are solely dedicated to the topic of .NET memory management and its Garbage Collector. With many, many internal workings of all this. I believe, personally, that there is currently no single book or even finite set of articles online that give so comprehensive insight into this topic. As a person who sincerely loves .NET a...
Wanna know a bit more about LOH? Let's examine it in today's post about a bit forgotten Large Object Heap :)
Sztuka programowania 2300 dni, 7 godzin, 18 minut temu 65 źrodło rozwiń
Wanna know what is fReachable queue, how finalization works in .NET and how to use a Dispose pattern? Come and read a new post in my .NET Internals series :)
Sztuka programowania 2307 dni, 7 godzin, 13 minut temu 45 źrodło rozwiń
Examining garbage collection in more details today. We'll see what is marking phase, actual collection process and heaps compaction to make it more efficient. Come and read! :)
Sztuka programowania 2321 dni, 7 godzin, 35 minut temu 66 źrodło rozwiń
Let's continue the .NET Internals series and see Boxing and Unboxing today :)
Sztuka programowania 2336 dni, 2 godziny, 19 minut temu 55 źrodło rozwiń
First, introductory post to my new ".NET Internals" series. Next posts will be published each Wednesday from today, so I invite you all to follow the series :) First post is the introduction to basic concepts of memory structure.
Sztuka programowania 2349 dni, 7 godzin, 26 minut temu 116 źrodło rozwiń
Reducing memory allocations from 7.5GB to 32KB Table of Contents Context of the problem Establishing a baseline Easy win 1 Easy win 2 Splits are never cool Lists are not always nice Pooling byte arrays Goodbye StringBuilder Skipping commas The war between classes and structs Goodbye StreamReader TLDR
Architektura 2390 dni, 2 godziny, 17 minut temu 163 źrodło rozwiń
A few months ago I wrote an article about Zero GC in .NET Core 2.0. This proof of concept was based on a preview version of .NET Core 2.0. However upcoming .NET Core 2.1 contains many improvements in that field so I’ve decided to write follow up post. I’ve also answered one of the questions bothering me for a long time – how would real usage of Zero GC like in the context of ASP.NET Core application?
Memory Visualizer wymaga udostępnienia języka zapytań odnośnie obiektów i struktur w pamięci. Jak pisałem w części Cypher, co to jest?!, język ten nazywam MQL - Memory Query Language. W istocie jest to jednak po prostu Cypher, który rozszerzę o elementy kontrolujące...
Daj się poznać 2016 3176 dni, 7 godzin, 32 minuty temu 42 źrodło rozwiń
While working as a developer within SharePoint – farm solutions, every developer has come across Memory Leaks, but what actually are memory leaks and how to defend your code from them?
This article is a continuation of my previous article. It shows how to create a custom intern pool that does not fragment the LOH and how to further improve it.
Today I would like to introduce you to Process Governor – a new tool I added to my .NET diagnostics toolkit. This application allows you to set a limit on a memory committed by a process. I wrote this tool to test my .NET applications (including web applications) for memory leaks. With it I can check if under heavy load they won’t throw OutOfMemoryException.