Mastering Memory Management in Node.js: Tips and Tricks for Better Performance

[@uncleiroh3616]

This video is a gem for those who want to learn a new thing or for those who just started server side development

[@SoftwareDeveloperDiaries]

Always happy to share such videos! Let me know in case if you ever have ideas :)

[@uncleiroh3616]

Do a video on threading, i think many of us would love to watch it.

[@yogeshmahale8389]

Awesome. I am looking for this video only...Now I am doing code review of junior developers very efficiently with this tips.

[@mr.h_arab]

most node ja useful video so far ❤️

[@aliadel1723]

I'm In love with this channel

[@NishantTomar-m2t]

Great insight and simplicity on each topic you represent. This series of advance node.js is just great. Hopping for more great content in this series.

[@SoftwareDeveloperDiaries]

Thanks! More to come :)

[@MAK_007]

What an excellent video. Thank you. I am currently watching all of your videos

[@SoftwareDeveloperDiaries]

Happy to hear, mate!

[@apurvwaghmare5974]

@@SoftwareDeveloperDiaries hello currently i am working on a project of encryption and decryption where i have file format like txt, jpg, mo3 and mp4 but for mp4 it gives heap out of memory and memory leak will this help me in resolving the issue as i have deployed my project on render ?

[@themixmaster]

That's a masterpiece bro, keep doing good stuff for us

[@Nick-wz6tz]

Omg thank you so much ! Needed this a lot

[@שחקדויטש]

Great video, simple, clear and to the point :)

[@judgebot7353]

just found your channel it's amazing man. Thanks a lot

[@SoftwareDeveloperDiaries]

Glad you enjoy it!

[@sparshturkane2550]

Nice explanation

[@Joel-do3oi]

Thanks for the tips!

[@dominggusoctovianus4915]

Nice work Gusgadirov. Would you mind to share this topic again but on client side especially using React? I would love to watch it.

[@SoftwareDeveloperDiaries]

Great suggestion, I'll take a look into it!

[@dominggusoctovianus4915]

@@SoftwareDeveloperDiaries Awesome

[@kvahh4290]

Thank you so much for this content, your teaching is excellent. Would you mind telling me what this blackboard app is?

[@GameON-Playstation]

it's called excalidraw

[@TheDuckPox]

Why would you clear the timeout you just created? I think the example only presents bugs since the setTimeout callback might never even has a chance to fire.

[@SoftwareDeveloperDiaries]

Great point, I didn't realize that!

[@SoftwareDeveloperDiaries]

Here's what ChatGPT says about it :d f the callback of your setTimeout doesn't perform any asynchronous operations and finishes quickly, you might not necessarily need to clear the setTimeout. In this case, the callback function will execute and complete its tasks promptly, without causing any delays or issues. The main reason for clearing setTimeout is to prevent unnecessary execution of the callback when it's no longer needed or to avoid any potential side effects caused by executing the callback after the client has already received a response or disconnected. If the callback is lightweight, performs synchronous operations, and completes quickly, it's less likely to cause any adverse effects. However, you should still consider the following factors: Server resources: Even if the callback finishes quickly, it might still consume server resources unnecessarily. If you have many such timeouts running simultaneously and frequently, it could potentially impact the overall performance of your server. Expected behavior: Consider whether it makes sense for the callback to run after the request has already been completed. If the callback's actions are related to the request/response cycle, it's better to clear the timeout to ensure that it doesn't execute inappropriately. Code maintainability: While a fast synchronous callback may not cause immediate issues, it might become problematic as your codebase evolves. Clearing the setTimeout ensures that the behavior of your code remains predictable and avoids potential bugs if your code logic changes in the future. In conclusion, if the callback finishes quickly, it might not immediately cause noticeable issues, but it's still good practice to clear the setTimeout to ensure proper behavior and code maintainability in the long run. It also helps adhere to best practices and makes it easier for other developers to understand and maintain your code.

[@Alfakatt]

Wait, did you just ask chatgpt for advanced topics and went down that path making these tutorials?

[@pabloroque8268]

Great video!

[@yogiHalim]

wow Thank you

[@maxhou8395]

Great video 🎉, very useful for me😊

[@SoftwareDeveloperDiaries]

Glad to hear! 🫶

[@WIBEDRILLMusic]

Can you please make a video on multi-tenancy in node js using any database like PostgresQL or MongoDB?

[@SoftwareDeveloperDiaries]

Will add this to my list 👌

[@643_sankettiwari5]

which tool he is using as the blackboard?

[@KasthuriarachichigePrasanna]

great

[@M0HCT3R]

Is clearTimeout actually needed in 9:48? The only role of clearTimeout is it to prevent setTimeout callback from to be called.

[@SoftwareDeveloperDiaries]

Yes and no. Clearing timers is a good practice, especially "setInterval"s. Although leaving a "setTimeout" won't really hurt as you said.

[@ulietaight]

​@@SoftwareDeveloperDiariesis it a bad practice to use setInterval like cron job, i mean if i need to call function 1 time per day, and i wont clear interval, because i need it

[@Lemmy4555]

@@ulietaight it's not, is actually the most efficient way since it uses internal timers. However depending of the requirement of your application you may need to use an external service dedicated to this kind of things.

[@sergeyplotnikov4303]

Thank you!!!

[@SoftwareDeveloperDiaries]

It's a pleasure!

[@EducationAllTheTime123]

Brother, I had a Node.js project, then we changed the method of connecting to SQL, and all the SQL queries slowed down. Later, we reverted to the old method, but it couldn't reach the old speed again. What can be done? (Windows Server | Mssql | Node.js)

[@SoftwareDeveloperDiaries]

Thanks for donating, my friend! That sounds strange, can you make sure that you are using connection pooling? If you are, but reverting to the old method caused a slowdown, then maybe it's caused by the database or the machine, rather than the code? It could just be a coincidence that the slowdown happened during the code change.

[@Tiberiumgod]

Do we really need to clear timeout even if it is executed? I thought that we need it only to cancel timeout.

[@amirghorbanian1300]

❤

[@akashchauhan1116]

"just to make sure My computed doesn't explode ...." 😂

[@ikronos4951]

“Always clear your timeouts” 😂 Didn’t you mean Intervals?

[@SoftwareDeveloperDiaries]

Both should be cleared 😛