Golang Performance Hack That Reduces GC Overhead

► Join my Discord community for free education 👉 / discord
► Learn Golang Mastery 👉fulltimegodev.com
► Learn how I became a self-taught software engineer 👉fulltimegodev....
► Follow me on Twitter 👉 / anthdm
► Follow me on GitHub 👉 github.com/anthdm
DESCRIPTION
------------------------
In this Golang tutorial I will show how you can utilize object pooling to reduce overhead on Golang's garbage collector.
SUBSCRIBE OR NO MARGARITAS
╔═╦╗╔╦╗╔═╦═╦╦╦╦╗╔═╗
║╚╣║║║╚╣╚╣╔╣╔╣║╚╣═╣
╠╗║╚╝║║╠╗║╚╣║║║║║═╣
╚═╩══╩═╩═╩═╩╝╚╩═╩═╝

[@anthonygg_]

► Join my Discord community for free education 👉 discord.com/invite/bDy8t4b3Rz ► Learn how to become a Golang master 👉 fulltimegodev.com Thanks for watching

[@NoTubeeable]

for anyone using standard libs, or libs with standard context - you don't need any of this. Simply don't create the new context, just reuse the one already provided by `r *http.Request`. In your handler simply instantiate your context by `ctx := r.Context()`. This will reuse existing context created by Request which is automatically tied to the lifecycle of the request

[@oussaber]

what if your server is getting 100 thousands of req/s , reusing the same context won't be an overhead?

[@markmcdonnell]

AHH, so there's already a context created as part of the request object itself, so you might as well use it, as its creation is outside of your apps control. That then makes this video redundant, right?

[@pepperdayjackpac4521]

@@oussaber wouldn't they be different contexts?

[@yarcat]

It's important to realize that r.Context() is the context of the request, and it will be closed either if the client closes their connection, or if the handler is done. Generally, it's a good practice to keep w and r objects only inside of the handler and never pass them further (except for your http helpers) You get your request, you parse it, validate it, execute an underlying logic. Potentially without any extra allocations at all, and without ever keeping the request/response refs, which is also very unsafe because of the internal io.Readers e.g. a Body()

[@fajarislami2515]

I don't understand, why do we set a value in the pool, then delete the value, and put it back? Doesn't that mean the context is only temporary?

[@something4074]

Since your Ctx struct only contains four pointers, my intuition would be that just allocating it on the stack and coping would be faster then using a pool. It's hard to determine with micro-benchmarks (I can contrive scenarios where each is faster), would be interesting to see that benchmarked in your specific case.

[@adityacariappa4494]

Love it, I am trying to build an open source Webhook as a service project with golang. Any tips would be appreciated ! Will update once I have MVP running. I like to build things just like you 👊

[@rutbirhanu4505]

Your videos are amazing can u please make video on many to many relation using gorm

[@eriknyk2k]

what's your VS theme name buddy?

[@anthonygg_]

Gruvbox

[@4lxprime730]

lets go

[@AyrtonGomesz]

You;re the best.

[@adibhanna]

good tip!

[@kylechen3386]

Thx❤

[@DerekCordeiro]

Switch back to VS Code? Any opinion on Zed editor?

[@PlanetoftheGaming]

If you don't publish the code it's impossible to understand, a tutorial should come with the code.

[@casper64]

Just watch the video and pause it if you need to. Copy pasting isn't going to learn you anything

[@anon-fz2bo]

Skill issue

[@NathanielBabalola]

Could you please add comments to your code

[@anthonygg_]

Why?

[@NathanielBabalola]

@@anthonygg_ lool