Garbage Collection [An Introduction in .NET 5.0]

Подписаться 27 тыс.

Просмотров 16 тыс.

50% 1

In this video, I am going to walk through the fundamentals of garbage collection in .NET Core/.NET 5 applications. The concepts are the same for all .NET Frameworks including the legacy .NET 4.* frameworks, but the internal implementation might be different.
If you have worked on C or C++ before, you know how painful it is to manage memory and how error-prone it can be. Garbage collection features of managed frameworks like .NET make life extremely simple.
In this video, I have misspoken a couple of times:
At 05:10 I mentioned "three different classes", which should have been "three different objects"
At 10:47 I mentioned "unmanaged method" which should have been "unmanaged objects"
The URL for IDisposable design pattern video is: • IDisposable Design Pat...
The index for this video is as follows:
00:50 - What is garbage collection
01:44 - Garbage collector details
02:45 - Managed heap
04:00 - Generations of the managed heap
06:02 - The three generations of the managed heap
07:16 - Large object heap
08:20 - Details about how does garbage collection works
My blog URL: dotnetcorecentral.com/
My GitHub repo: github.com/choudhurynirjhar

Наука

Опубликовано:

16 янв 2021

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 27

@DotNetCoreCentral 3 года назад

In this video, I have misspoken a couple of times: At 05:10 I mentioned "three different classes", which should have been "three different objects" At 10:47 I mentioned "unmanaged method" which should have been "unmanaged objects"

@ibrahimblake1219 2 года назад

instablaster

@DotNetCoreCentral 2 года назад

@@ibrahimblake1219 thanks for watching!

@spencer_mayne 2 года назад

Really well explained. Great video

@DotNetCoreCentral 2 года назад

@ Spencer Mayne, thanks for watching!

@kumar_codes 3 года назад

Your videos are very helpful keep making just like this...The content in it is very good..

@DotNetCoreCentral 3 года назад

@Pritish Ranjan, thanks for watching!

@shrikantmule9812 2 года назад

Great video 👍🏻

@DotNetCoreCentral 2 года назад

@shrikant mule, thanks for watching!

@littlebearjeremy 2 года назад

Nice video. well done

@DotNetCoreCentral 2 года назад

@X R, thanks for wathcing!

@mahendranchinnaiah7593 3 года назад

Thank you

@DotNetCoreCentral 3 года назад

@Mahendran Chinnaiah, thanks as always for watching!

@sidranoor6891 3 года назад

is there any website or blog of yours on this topic ? can your share the link

@DotNetCoreCentral 3 года назад

@SIDRA NOOR, thanks for watching! My blog site URL is dotnetcorecentral.com/, though I do not have this captured in my blog yet, I have other topics there if you want to check out.

@saurabhchauhan232 3 года назад

Thank you ! Question: In .net core DI, we register Transient, Singleton, Scoped. Creating transient and scoped isn't adding additional burden on GC? though singleton is not good option either but this really confuse me, can you please answer if you can?

@DotNetCoreCentral 3 года назад

@Saurabh Chauhan, thanks for watching the video! Singleton is not necessarily a bad thing if it is done through DI, the reason the singleton design pattern was drawn upon was because of the fact that it was harder to test. But if you use it through DI, that argument is not valid anymore. There are definitely cases for using a singleton, especially if there is no state managed inside the object. Now in terms of transient and scoped usage, well technically they might cause GC to run more often compared to everything being singleton, but there are cases for using these as well. I will not be too concerned about GC running multiple times, especially in the days of microservices where services are small. But if you are using a monolithic application, there should be some consideration given for this situation. In which case, you should debate about which all classes make sense making singleton vs not. Let me know if it makes sense. Thanks

@saurabhchauhan232 3 года назад

@@DotNetCoreCentral Yes this make sense but that's where my concern is with Monolith, what should be the prime consideration to decide which service should be scoped vs transient vs singleton

@DotNetCoreCentral 3 года назад

@@saurabhchauhan232 As long as the object does not maintain any state, meaning it does not have any concern of multi-thread contention issues, it can be a singleton. Or it really needs to be singleton due to business needs, and need to manage state, in which case you need to care for thread contention. In other cases, it can be transient.

@saurabhchauhan232 3 года назад

@@DotNetCoreCentral Thank you for your reply, Sorry but what I have understood so faf is singleton is for managing state and transient is something that has nothing to do with state

@DotNetCoreCentral 3 года назад

@@saurabhchauhan232 I am planning to create a new video on this, hopefully, that should answer your questions.