#garbage-collection articles

MMMayank Mahajanmayankdev.hashnode.devOct 1 · 12 min read

Java Explained Simply: Why It Runs Everywhere (and How)

You're about to type System.out.println("Hello, World!");. Wait. Java has powered banks, e-commerce backends, Android tooling and big-data platforms for almost three decades. The reason isn't its synt

0

SASharafath Alisharafath.hashnode.devJun 8 · 9 min read

My Node.js Server Was Leaking Memory in Production. Here's How I Found It.

Our Node.js server was crashing in production. Not once — every single instance was going down, one after another, and Sentry (logging) was flooding with alerts. We had auto-scaling configured with a

0

PKPatrick Kearnsdotnetdigest.comJun 6 · 20 min read

The GC Wall

A .NET API can be fast, clean and perfectly reasonable at normal traffic levels, then start falling apart when load increases. The strange part is that nothing obvious has changed. The database still

0

CDCoding Dropletscodingdroplets.comMay 28 · 14 min read

ASP.NET Core Intermittent Latency Spikes in Production: GC Pressure, ThreadPool Starvation, and Connection Pool Root Causes and Fixes

Intermittent latency spikes are one of the most deceptive production problems in ASP.NET Core. The API runs fine under low load, all your unit tests pass, and local benchmarks look healthy - then unde

0

AAAbstract Algorithmsabstractalgorithms.hashnode.devApr 10 · 25 min read

How JVM Garbage Collection Works: Types, Memory Impact, and Tuning

TLDR: JVM garbage collection automatically reclaims unused heap memory, but every algorithm makes a different trade-off between throughput, latency, and memory footprint. The default G1GC targets 200m

0

HHasblog.hsnits.proMar 15 · 8 min read

Fundamentals of Garbage Collection

1.Introdiction to .NET Memory Management When a .NET application runs, memory is primarily divided into two areas: Stack Heap Local variables and method calls are handled by the Stack.Objects crea

0

AEArda Erenardaeren.hashnode.devAug 4, 2025 · 14 min read

Crafting Hybrid Systems: Beyond the Language Wars in Modern Software Architecture

TL;DR: The "Node.js vs. everything else" debate misses the point. While critics focus on traditional limitations, modern teams are building hybrid architectures that combine JavaScript's development velocity with native-level performance through Prot...

0

SSSergey Shishkinserj-aleks.hashnode.devMar 14, 2025 · 1 min read

zap ... *Zap ... zap_ ... zapTree

zapTree, рекурсивно удаляющую структуру дерева из базы данных, уже рассматривалась в контексте символа tree. *Zap - глобальная переменная, содержащая список и путь. Если они заданы, а значение *Solo равно NIL, внешние символы, которые больше не досту...

0

NKNivedita Kumaritechadora.hashnode.devFeb 25, 2025 · 3 min read

Why does Java use a generational garbage collection approach instead of treating all objects the same during garbage collection?

The generational garbage collection approach in Java (used in the JVM's Garbage Collector) is beneficial because of the weak generational hypothesis, which states: Most objects die young – The majority of objects are short-lived and become unreachab...

0

IIInterview Insightsdifference-nal-nally-and-nalize.hashnode.devJan 29, 2025 · 3 min read

Understanding the Difference Between ﬁnal, ﬁnally, and ﬁnalize in Java

Java provides three distinct terms—ﬁnal, ﬁnally, and ﬁnalize—each serving difference purposes. While they may sound similar, their usage varies signiﬁcantly in Java programming. In this article, we'll break down their functionalities, use cases, and ...

0

#garbage-collection

#garbage-collection

Explore Hashnode

Trending tags this week

Java Explained Simply: Why It Runs Everywhere (and How)