Відео

Haha! Thanks for the feedback. I'd work on this in the further videos. Keep watching and hope you found the content useful

Bahut bahut dhanyawad bhai saab! Happy learning :)

Thanks for watching, I am glad you liked it :) Happy learning.

Thanks for your comment Ankit! I have it planned, will make a video on this soon :) Keep watching and learning, thanks!

@@shandilyacodes Desperately waiting for it ;)

I have it planned for upcoming months, keep watching :) Thanks for your comment!

:) Glad you found it helpful! Thanks!

Thanks for your comment, I am glad yo found it helpful :)

Noted! I'd try to cover this topic on my channel :)

Thanks for your comment, I am glad yo found it helpful :)

Thanks for your comment, I am glad yo found it helpful :)

Thanks for your comment, I am glad you found it helpful :)

So here is how it goes. In Java implementation of ConcurrentHashMap, write operations like put or remove acquire exclusive locks on specific segments (or buckets); it ensures thread-safe updates by preventing other threads from modifying the same segment. However, it allows multiple segments to be updated simultaneously, enhancing concurrency (Understand this as locking is done on a per-segment (or per-bucket) basis). Read operations like get are lock-free, leveraging volatile variables to ensure visibility of the latest data, allowing multiple threads to read concurrently without contention. Hope this helps :) Thanks for watching!

@@shandilyacodes first of all thank you so much for sharing the detail. so there can be multiple locks acquired on different buckets (one lock per bucket) for writes and for reads there are volatile variables to ensure visibility from shared L3 cache as you taught.

Thanks for your comment, I am glad yo found it helpful :)

Yes, putting wait in loop could lead to busy waiting, this was done only to show and demonstrate the current video example :) Thanks for watching and sharing your thoughts!

Thanks for your comment. I am glad you found it helpful :)

Thanks for your comment, I am so glad you found the tutorial helpful :)

Thanks for your comment, hope this was helpful. All these topics are planned and in pipeline :) They are coming soon!

Or synchronized(private static object)

Sure! I'd try to create a video on this, but for now to answer your question find the answer below When you use synchronized(this), it locks the current object (this) for synchronized access. It ensures that only one thread can execute synchronized code blocks on this object at a time. When you use synchronized(otherObject), it locks the specified external object (otherObject). It allows synchronized control over a different object, not just the current instance. Use synchronized(this) for instance-level synchronization and synchronized(otherObject) when you need to coordinate threads across different objects or shared resources. Hope this was useful and answered your question! :)

Thanks for you comment. I am glad you found it helpful. I have plans to make an elaborated series on Spring Security, please stay tuned :)

Thanks for your comment :) I am very glad you found the playlist useful. Please keep supporting my work by subscribing, liking and sharing the videos :)

Thanks for your comment :) I am glad you found it helpful, happy learning!

Thanks for your comment. Yes, sending the ids and LLM response in each conversation indeed does blow up the context window. That's why I suggested one approach where we can use the LLM itself to summarise the discussion so far in short if the context window goes beyond certain size. Other approach is to be track only a few of the last conversations, but downside is LLM could lose track of the previous details, for example, we have had 100 conversations in a thread, but we are tracking only last 25 conversation, so depending on how related things are loss of the previous 75 conversation could lead to uncertain response. Other approach could be create some sort of relation (a directed graph may be?) between the conversation, and use that wisely as needed. So given that LLMs are stateless, idea is to get as creative as possible to get the most optimal result without blowing up the token cost :) Hope you found the video and this comment useful. Thanks!

@@shandilyacodes Thanks for replying back, interesting to hear your thoughts on this. Could you please suggest how the `ChatMemory` object of Spring AI package can help in this regard.

Thanks for your comment Jyoti! Glad you found this helpful. Sure, I'll try to cover LLD question involving concurrency in future :) Also, if you have topic in mind related to LLD involving concurrency, please suggest, that'll help me in deciding on the topic better.

@@shandilyacodes yep,Can you make video on Pub Sub Model

Thank you for your comment :) I am glad you found the explanation excellent! Yes, I have extensive plans to cover system design as well. I will be releasing extensive playlists covering basic operating system concepts, networking concepts, which will be followed by System design in coming months. Stay tuned!

@@shandilyacodes thankyou

Hello! Thanks for your comment. I am using Intellij Idea with material theme :) Please subscribe my channel if not done already to support my work!

@@shandilyacodes thank you brother, i already subscribed and perfered to my friends. Your playList is more helpful to understand this concepts.

@@kalaiarasanpa Thank you! :) Appreciate your help and support!

Thanks for your comment, I am glad you liked my video :) Sure, an extensive series on micro services, design patters is in pipeline :) If not done already subscribe my channel to support me!

Thank you! Glad you liked it.

Thank you! Glad you liked the tutorial. I am using Intellj Idea with some customisations on a Macbook. Please subscribe if not done already :)

Glad that you loved the explanation. Please tell me what topics you want tutorial on, I'd add them to my todo list and will surely make videos on those. Thanks for watching, if not done already please subscribe :)

@@shandilyacodes I've already subscribed ! Following Topics Are required: Servlet, JDBC, RDBMS(MYSQL) Thank You Sir !!

@@RajKhade-r1h Sure thing!

It's material theme with a background set to some transparency 😊

Glad you found it helpful 😊 Do subscribe for more content 😅

Ah, I realized the prompt history just contains the question part, not that much then

Thanks for your comment and I am glad you found the video helpful. To answer your question, yes, all that you send in the conversation context would be counted towards total token consumption and will cost money. One workaround to this is with two combined approaches 1. Keep only a range of last 'few' questions and answers in the discussion for the context. For example, last 7 questions and their answers 2. Summarise the discussion so far so that LLM has the context but less tokens are used Ofcourse, both the approaches have their own pros and cons, but for some one who is on a budget and wants to play around, these two approaches are good starting point. If it was helpful, please do consider subscribing my channel, thanks again!

Thanks for your comment. I am glad you liked. If not done already, I request you to please subscribe and help the channel grow :)

Thanks for your comment and glad that you found the content helpful :) Pls subscribe if not done already! If you like the prompt, today I'll be releasing a video on using Prompts with Spring AI, hopefully you'd like that as well :)

Haha :) Can relate! Spring AI is fun.

Thanks for the comment buddy, I already have a Playlist in progress on Spring AI module. I try to add atleast tutorial on atleast one topic every two days. Have covered two topics 1. How to setup Spring boot project for chat completion api using open ai key and 2. How to give memory to a conversational AI to retain the context of a conversation. Here is the link, ua-cam.com/play/PLG-dyv583o8woeeMV5N08X-sE3jz0vJ6o.html , check it out :)

Sorry brother! This video is about making Spring AI applications, I am not sure what you are asking here. Let me know if you have any questions relevant to this video. Thanks.