You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the article, Satori GC is still in the experimental stage, but it appears to include features required in high-performance scenarios, such as:
A low-latency mode that disables compaction
Disabling of Gen 0
Major GC processes run in parallel with application threads, so except for compaction, application pauses are not required
Switching from a C# managed engine to a C++ native engine seems to be a reasonable decision at this point. However, I feel that a managed engine itself is highly challenging and valuable. In the future, I expect that improvements in GC will enable stable operation with fully managed code.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The following is a commentary article about GC.
(Original) https://qiita.com/hez2010/items/e0a3573ecb3b14325336
(English Translation) https://qiita-com.translate.goog/hez2010/items/e0a3573ecb3b14325336?_x_tr_sl=ja&_x_tr_tl=en&_x_tr_pto=wapp
According to the article, Satori GC is still in the experimental stage, but it appears to include features required in high-performance scenarios, such as:
Switching from a C# managed engine to a C++ native engine seems to be a reasonable decision at this point. However, I feel that a managed engine itself is highly challenging and valuable. In the future, I expect that improvements in GC will enable stable operation with fully managed code.
Beta Was this translation helpful? Give feedback.
All reactions