/explore
|
You are here 
|
psy-lob-saw.blogspot.com | ||
| | | | |
blog.ragozin.info
|
|
| | | | | Stop the world pauses of JVM due to work of garbage collector are known foes of java based application. HotSpot JVM has a set of very advanc... | |
| | | | |
nora.codes
|
|
| | | | | [AI summary] The article explains the concept of 'unsafe' in Rust, clarifying that it allows specific low-level operations while maintaining overall memory safety through the language's type system and safe abstractions. | |
| | | | |
richardstartin.github.io
|
|
| | | | | In the JVM, lots of evidence of garbage collection mechanics can be seen from JIT compiler output. This may be obvious if you think of garbage collection as a task of book-keeping: the various auxiliary data structures used to track inter-region or inter-generational references, relied on for faster marking, need to be kept up to date somehow. These data structures need maintenance, and this isn't something you control in application code: the maintenance aspect must must be instrumented somehow. If you profile your application's disassembly, you can find artifacts of the various garbage collectors, and these snippets of code can help you understand the throughput tradeoffs of each collector. You can also just read the documentation. | |
| | | | |
antonym.org
|
|
| | | Memory management in low level code has changed slowly over the years. Intraditional C code, you would allocate memory with malloc() and release itwith free(). | ||
