Ranjith ramachandran

Пікірлер

@DhineshM-l3k Сағат бұрын

Watching this in 2024, Amazing video.

@sachdevasahil7 3 күн бұрын

Love your videos. Learn alot and new things keep up the good work thank you

@Tanga-ou5im 5 күн бұрын

Best explanation. Perfect

@VinothkumarJayandiran 28 күн бұрын

Thanks Ranjith for the detailed explanation. Appreciate it.

@curio78 Ай бұрын

absolutely useless feature added to a language. Instead of giving value type they gave something that they cannot explain what for?.. what is that this can do a class cannot? Nothing. Is it faster being value type NO so useless in that too. Like someone without vision as allowed control of java to mess with it. Just for everyone .. avoid this at all cost. And wait for value type to come in project Valhalla.

@ranjithramachandran5928 Ай бұрын

Brian Goetz had summerized this as use cases for "value records"

@curio78 Ай бұрын

@ranjithramachandran5928 value records are the same as value classes. So what are records for? They could have simply given modifier that says public read only. It would have made 1000 times more sense. There is one simple reason why it was added. Design by committee with no central vision for the language direction. The most critical of all the language changes that was needed was universal generics. Yet it's been 7 years, and project Valhalla has not been delivered yet. The question is such delay can be considered reasonably explainable. For the reason java missed all the datascience boom was because of that.

@ranjithramachandran5928 29 күн бұрын

@@curio78 Records and value-based classes have different restrictions; records enhance the usual programming model - yes agree that no performance benefit etc. But a huge win for developers since the last LTS release. Value-based classes are about giving up identity to get better performance. Records are for regular use, while the value types are isolated from the regular(identity) world.(example construction + inheritance, locks, etc)

@curio78 29 күн бұрын

@@ranjithramachandran5928 You described value class benefit. But left out the benefit or Records. When you say it enhances usual programming model what does that even mean? That it saves you 3 lines of getter method code per private field? How exactly is that benefiting any programming model. In fact most data objects needs to be updated one or other fields. what happens then? you need to rebuild the entire Record now? If there was a benefit similar to value class of performance then its a compromise that's understandable. But given there is no benefit of any performance. In short, Records are just dumb way to implement this. Records are an example of anti pattern. which simply look like doing something better on the surface until you dig into use cases. It will take project Valhalla to rescue this anti pattern to give some meaning to it as a short form for writing value DTOs. The very idea of Final fields is to take advantage of treating Records as data and not Objects. But Records are by design not that right now. So WHY?

@programacion3694 Ай бұрын

very good explanation dude, you are amazing :)

@programacion3694 Ай бұрын

uwu

@programacion3694 Ай бұрын

owo

@stevenonymous82 Ай бұрын

Such a high quality introduction, thank you kindly!

@vinayak6564 Ай бұрын

Isn't low latency directly proportional to throughput? low latency means requests are served fast, which means a greater number of requests can be served in a given time, which in turn leads to high throughput? In this case how pause time acceptable for throughput?

@AayushGore- 2 ай бұрын

ClassDefNotFoundException definition at 11:29. Thanks sir!

@m07hcn62 2 ай бұрын

Outstanding ! Thank you, Sir.

@blazekiller521 2 ай бұрын

Awesome Explanation ❤❤❤❤❤ Please Keep On Doing Good Work Why Exactly You Have Stopped Uploading Such A Great Work

@blazekiller521 2 ай бұрын

Awesome Explanation ❤❤❤❤❤ Please Keep On Doing Good Work Why Exactly You Have Stopped Uploading Such A Great Work

@468hitman 2 ай бұрын

nicely explained

@S__Khan__ 3 ай бұрын

Thanks Ranjith. Quite clear and in-depth explanation.

@sreenivasuludoniparthi7534 3 ай бұрын

It's amazing tutorial and great explanation

@mystoriesuk 3 ай бұрын

Thanks!

@er.sahilmd 3 ай бұрын

Hey Man, I really appreciate your Hash Map like videos very much They are really very beautifully explained, can you please continue on such topics. Like most asked interview questions playlist.

@pratikbutala9044 4 ай бұрын

Watching this in 2024. Amazing information on GC fundamentals. Thank you! 👍👍

@er.sahilmd 3 ай бұрын

Same here

@channuangadi7504 4 ай бұрын

16:00 is it compulsory always the the targeted object move from Eden--- survivor1---- survivo2 Is steps matters always?

@ranjithramachandran5928 4 ай бұрын

The two survivor spaces are used to avoid fragmentation. Move to E->S1 and then from there to S2 - only one of them holds objects at a time.

@AbhijitDixit-ki1oo 4 ай бұрын

Use of animation really helps understand the concept. Thank you so much sir 🙏

@aruneshshah7402 5 ай бұрын

Now in 2024 and this is still relevant. Woow

@Sreeni_JavaTechie 5 ай бұрын

Informative video. Please correct to cloneable interface instead of clonable

@gulamsarwar7502 6 ай бұрын

would you pls share your slides ??

@Vk-bq8sd 6 ай бұрын

still a masterpiece

@shubhammatsagar2344 6 ай бұрын

02:30 Objects are created and collected based on their lifespan in the application. 07:15 Garbage collection involves marking reachable objects, sweeping unreachable objects, and compacting memory. 09:40 Java heap is divided into young and old generations for managing objects efficiently. 14:48 Survivor spaces in Java heap prevent the need for compacting step 17:11 Garbage collection in Java manages unreachable objects efficiently 21:33 Difference between responsiveness and throughput in Java applications 23:33 Concurrent collector runs concurrently with the application, while Parallel collector uses multiple CPUs for fast garbage collection. 28:08 G1 garbage collector in Java 7 & 8 divides the heap into regions for faster and minimal pauses. 30:20 Garbage collection in Java includes four different kinds of garbage collectors and how to use them. 35:08 Garbage collection in Java has no guarantee on when objects will get collected. 37:14 Garbage collection parameters in Java 41:39 Visual VM allows manual triggering of garbage collection. 43:46 Using direct buffer memory for managing Java Runtime memory Crafted by Merlin AI.

@scottloewke5199 7 ай бұрын

In order to use the "hash & (n-1)" optimization in place of a modulo operation, n needs to be a power of two. The video presenter kept saying "2 raised to n", which isn't correct.

@vyshnavramesh9305 7 ай бұрын

Summary: Steps in garbage collection: mark, sweep, compact Division of heap into Young (Survivor spave from, Survivor space to) and Old generations Minor garbage collector runs mark and sweep in young generation Major garbage collector runs mark, sweep and compact across the heap Types of GC: Serial (single thread - stops app during MSC), Concurrent (runs CS along with application) and Parallel (multithread - stops app during MSC)

@vyshnavramesh9305 7 ай бұрын

0:49 Edit .java -> compile .java -> run .class 3:33 JVM breakdown 4:14 Class loader: load (bootstrap (rt.jar), extension (jre/lib/ext), application (classes we write)) 6:59 Class loader: link (verify bytecode, prepare memory allocation for static variables, resolve nested references of a class) 10:02 Class loader: initialize (of static variables, static blocks) 11:09 ClassNotFoundException and ClassDefNotFoundException 12:38 Runtime Data area 13:01 Method Area / Permgen space / Metaspace (class data like static variables) 16:16 Heap (object data) 17:41 Program Counter Register: pointer to next instruction to be executed per thread 18:35 Java Stacks: stack frame of currently running method per thread 20:16 Native method stack: for running non-java methods called from java methods running in Java Stack (per thread) 24:09 Execution engine: GHIJ (Garbage Collector, Hotspot Profiler, Interpreter, JOT Compiler) 24:26 Interprets and executes the bytecode/instruction 25:52 JIT Compiler: Bytecodes that are repeated, called hotspots, are saved from re-interpretation. On the fly compiles them and make them ready for execution 26:27: Hotspot Profiler: graphically analyses the all the bytecodes and helps JIT compiler 27:36 Recap 26:57 Garbage Collector: cleans up unused classes, objects and memory areas.

@dhineshm4798 7 ай бұрын

Watching in 2023, its really super.

@nileshshinde-eb3gi 7 ай бұрын

Why you have stopped making videos... We need more content like this in Java🙂

@bahibrahim101 7 ай бұрын

Thank you

@nehapatel1133 8 ай бұрын

Hi Ranjith. Glad to see you back. Happy to hear your voice again. Can you please give your LinkedIn URL in comment section so we can follow you. Expecting more content on Java 17 and higher versions and Microservices.

@nehapatel1133 8 ай бұрын

Thank you so much for coming back. I don't know where were you all these years. I was checking your channel like anything hopping for that you would come one day. Thank God ! At last you are back. Please do not disappear. Loved the way you explain Java. Thank you Sir and welcome back!

@sowmyvasudevan1522 8 ай бұрын

If the main thread has a timeout set,is it possible that the gc at times can cause the timeout?? As in as gc kicked in main thread couldn't finish in time

@PURANDARLIVE 8 ай бұрын

CDAC Madhura mam ke reference se kon kon aya hai bhai ?

@sandipbhaumik 9 ай бұрын

Difference between -XX:NewSize and -XX:MaxNewSize is that, first one for initial space allocated for eden space and second one for max space allocated for eden space.

@norbertmao1373 9 ай бұрын

appreciate how you broke down the different types of GC algorithms. This is a must-watch for anyone looking to improve their understanding of memory management in Java.