I got 10x faster performance from this simple Node.js refactor 

Rust have the "image" crate, if you have never written Rust you are gonna enjoy it a lot, or die because the borrow checker.

I made one, I tried to comment it here two times, but it keeps getting deleted. thales-maciel/opt101

Thanks man yeah, I’ll be honest. Sometimes it’s hard to teach when you don’t know the skill level of your audience so I just kind of throw things at the wall and hopefully it’s good.

@@WebDevCody it is, really, good. i appreciate the content! been trying really hard to understand the "black box" of how the tools i use work (i.e. react, nextjs, node, supabase/postgres)

love you!

this is the state of web dev in 2024 everyone still using JS ...

What makes js good is what makes it bad.

@@waleedbukhari8988 just stop bro lol. It's not a language that should even exist in 2024 given the current state of technology

@@waleedbukhari8988 I used to be very charitable to javascript for many years, but recently I haven't had to use it much (I've just been continue to use Go and dotnet) and honestly going back to javascript for the first time in over 6 months has really shown me how brittle and hacky javascript is.

Same with python lol ​@perc-ai

you must be proud of own incompetence, if you saying this out loud lol

​@@Ss-zg3yjWTF....

its not even close

@@hamm8934 I am 100% sure multi-thread Node will beat any single-thread. stop clowning

@@Ss-zg3yj prime has a video of this. Its not even close. Controlling for hardware and code structure parity, Go is >60x faster than node, especially in long running services with high active clients due to node’s over reliance on the heap. Node is honestly so slow unfortunatey

Im mean its all about what works for you. Its much easier to write everything in js but it has its downsides. As does go. Pick your poison

@@hamm8934 prime hates JS. he also likes HTMX 🤡

What do you mean Node excels in I/O?

@@vinialves12362 The non-blocking async model and incredibly fast/flexible JSON (de)serialization

Or use Typescript knowledge to learn C# and you can do all this in one language.

@@naughtiousmaximus7853 Fair, C# and Kotlin are growing on me. That being said, TS/JS are more flexible and Go is faster / simpler / uses less memory

​@@naughtiousmaximus7853exactly what I've been doing for the last 10 years ❤ I try to stay away from any server side JS implementations as much as possible, but sometimes man's gotta do what man's gotta do. Go is a fun language though and I've used it for a bunch of algorithmic stuff. But for backend it's just not powerful enough as a language. Like no LINQ, inferior generics, no expression trees... imperative-only code is surely simple, but it's also jumpy and bug-prone, as you have to use a lot of statements to achieve you goal - let's say - to build a projection from a slice. Whereas in C# it's just a single functional (multi)line of LINQ proceeding from top to bottom.

JSDoc?

I ran into this exact issue. I was writing in TS and compiling to single file in a docker image. Had to change it so it keeps the file structure and guarantees I know where the file will be. Atrocious.

context.translate(x,y)? Not sure if that re-draws but may be faster.

yeah I could try that

All workers use its own canvas

I keep them alive on the real app, this was just an example

@@WebDevCody can you provide some code example of how you reuse the workers on the real app please?

@@maxmaximus7773 just don’t terminate them. They’ll remain running and listening for messages, so just keep sending messages to them

Klack app

the go runtime has a built in scheduler, so yes go routines are not always separate dedicated threads, but they are processed from a thread group I believe

If I need scale I’d run my docker container on a lambda and give it 10gb of memory. It should work just fine

Was just looking into this as I am nearing the launch stages of an app I've been working on. In Node.js, you can use Clusters. These are sort of like threads, but they are individual Node.js processes. When your app starts, you can spin up x amount of clusters of your API in order to consume all the cores on the machine. Beyond that, you'd probably need to spin up new servers.

@@gamingbud926 little different from what I’m trying to do here. That’s scaling a single machine to handle more api requests, I’m scaling a single endpoint to do its cpu intensive tasks faster

yes it really is

That is a possible thing I could look into. There is a way to stream to ffmpeg. All of these images can eat up a lot of memory for longer videos, so I felt it was safer to put them on disk until ffmpeg kicked off

I don’t know if it’s possible to do in the browser, but it might be that’s an interesting concept. I should look into yeah right now it’s for building out videos and TikTok shorts and stuff. I’m just trying to play around with. I have some fun though.

Idk it’s a mac book

@@WebDevCody They have to be brave!

bearded theme feat web dev cody

@@WebDevCody is this available for download? I want this theme for my vs studio. Edit:- found it thank you so much

Should have watched till the end before commenting lol

Bearded theme fest web dev cody

only for IO related tasks such as network requests, reading / writing to files. Something like drawing to a canvas which is very cpu intensive it will not

@@WebDevCody ah yes HTTP aside, actually processing things - JS shouldn’t REALLY be used for this if possible but suppose front end devs have to?

@@cianwalker1829 why not? If it does what I need but take maybe 5 seconds longer, why would I introduce more complexity on a project by bringing in yet another language and ecosystem when node was able to solve the problem? If at some point I really need to squeeze out performance, then sure I’d spent a month learning go and hoping they have packages already already for me to do canvas operations like this. But that’s also a risk because I may spend all this time just to find using a faster language wasn’t even that much faster, and now I’ve lost a month of dev time

@@WebDevCody sorry yes I meant what I said as a question more than a statement.

@@cianwalker1829 oh, to answer your question then, node works fine and runs millions of services around the world currently.

Primeagen had a video like this with websockets

Yeah, I wanna try if I get time

Pretty sure may be massively faster in a compiled language

They use a thread pool under the hood for io. We all know what I’m talking about.

@@vinialves12362 yeah it’s a bit rough

Might be worth looking into that. The issue is with ffmpeg I point it to a directory and it combines all my images into a video. I’d need to look into streaming into ffmpeg I think

Not recreating, this is built into node

@@WebDevCody right, I didn't mean that in the literal sense

I’ll try to remember to check it out

I round robin to the workers. Gpt calls this a binary semaphore. Whatever it’s called, it helps limit work in progress and that’s all I care about.

​@@WebDevCody you haven't reach the ceiling yet, also need a bit of work with the graph.

@@bokunochannel84207 ceiling for the workers being able to process more? Not sure what you mean

​@@WebDevCodyyea i mean, a binary semaphore is basically just a mutex lol

Who would have thought?! Usually I just overclock my ec2 instances so the electrons fire faster!

I invented concurrency

wait, it took 50 seconds without this change, and ran in under 5 seconds after the change. what's 50 / 5? 10 🤣

@@WebDevCody Was talking only about moving the work to workers, stopped after that due to the title assumed it was the only optimization you were going to do. My bad. I"m sorry. That said, it's still not 10x faster 😅. You started with 43 (not 50) and ended with 5.3 (not counting the runs without logs because that effectively gives you a different output), so that's about 8x times faster.

@@lengors7327 😜 you got me, I might have done some rounding

You don’t think bringing in another language in another ecosystem is not adding its own complexity?

flex

LET'S GO! good job babe

Doesn’t do anything for cpu intensive tasks. It only helps for IO bound operations.