I could feel my brain trying to stop me writing what I knew was an infinite loop but I did it anyway. I trusted you Jeff!

Fun nerd trivia: - A single CPU core runs multiple instructions concurrently, the CPU core just guarantees that it will appear AS IF the instructions were run serially within the context of a single thread. This is achieved primarily via instruction pipelining. - A single CPU core often executes instructions totally out of order, this is unimaginatively named "Out Of Order (OOO) execution". - A single core also executes instructions simultaneously from two DIFFERENT threads, only guaranteeing that each thread will appear AS IF it ran serially, all on the same shared hardware, all in the same core. This is called Hyperthreading. And we haven't even gotten to multi-core yet lol. I love you content Jeff, the ending was gold!

That chef analogy about concurrency and parallelism was genius. Makes it SO much easier to understand the differences.

Also when we say "one-core," that means "one-core at a *time*" -- computer kernels are concurrent by default, and the program's code will actually be constantly shifting to different CPUs, as the kernel manages a queue of things for the processor to do. Not too unlike the asynchronous system that javascript has, kernel will break each program you're running into executable chunks, and has a way to manage which programs and code get more priority.

It's a pretty good overview on how much more of a clusterfuck the code becomes once you add workers to it. And it didn't even get to the juice of doing fs/database/stream calls within workers and error handling for all of that.

Moments like 0:52, the short memorable description of callback functions, is what makes you a great teacher. Thanks man!

Love to see jeff going in depth on this channel, would love more videos like this one.

6:13 To see how all of your cores utilizing, you can change the graph from 'Overall utilization' to 'Logical Processor' just by right clicking on the graph -> Change graph to -> Logical Processor.

Thanks for shouting out code with ryan! That channel is criminally underrated

I am stuck step programmer 😂😂

That ending was possibly one of your best pranks ever, a new high watermark. Congratulations 😂

i watched a similar video early this year, but your way to deliver content is amazing, keep going

I'd like to see a video on JavaScript generators and maybe even coroutines.

Lots of comments about memorable descriptions, shoutout to the thread summary at 3:30. Your conciseness is excellent.

Really cool, I actually saw the other video about nodejs taking it up a notch when it came out.

talking about multi-threading data oriented design always helps

the `threads` package makes working with threads much more convenient. it also works well w/ typescript.

although it's called concurrent, schedulers still can only work on one task at a time. It will delegate a certain amount of time to each task and switch between them (context switching). The switch Is just fast enough to make it seem truly "concurrent". If a task takes longer than the delegated time, the scheduler will still switch and come back to it to finish.

aside from the outstanding quality, this ending was quite funny and hilarious! keep it up, your content is TOP 🙇🚀

Little known fact, you can also do DOM related operations on another thread. You have to serve it from a separate origin and use the Origin-Agent-Cluster header, and load the script in an . But you can still communicate with it using postMessage, and avoid thread blocking with large binary transfers using chunking. This is great for stuff that involves video elements and cameras. I use it to move canvas animations (that include video textures) off the UI thread, and calculating motion vectors of webcams.

just a heads up for your CPU; the 12900K doesn't have 8 physical cores, it indeed has 16, 8 performance and 8 efficiency cores, the performance cores have hyperthreading enabled but not the efficiency cores so you have 24 threads in total

ayo , was learning event loop and had a bit of confusion about performance b/w single and multithreading and jeff just posted the video at the right time.

Task Manager --> Performance tab --> CPU --> Right click on graph --> Change graph to --> Logical Processors

the cook analogy was great and i now understand

Yes Yes Yes, and exactly extra Yes! Thank you Bro for this contribution! You are speaking out of my brain! Best Regards!

¡Wow! Just yesterday I was watching some videos about worker threads because I will use them to speed up the UI in my current development 😄

It would be nice if you right click on the cpu graph and *Change graph to > Logical Processors*, so we can see each thread separately. Thanks!

You can also pass initial data without needing to message the thread to start working, however, that one I feel like its better to use for initialization like connecting to a database.

great topic, thanks 👍

Thanks, now I know what script I should include in my svgs

Adding more cores might still provide gains in a VM scenario depending on the hypervisor. As long a your VM isn't provisioned all physical cores the hypervisor is at liberty to utilize more cores and even up to all physical cores for a short amount of time resulting in increased performance for bursting tasks

Niiiice we have the exact same machine! (And thanks for the video!)

It's like you read my client's requirement and came into support

My brain: dont run it 8 years of programming: dont run it the worker thread registering my inputs to the console as I type it: dont run it Jeff: run it. **RUNS IT**

Good vídeo! Next time change the CPU graph with right click to see each threat graph. Hope it helps!

Amazing🔥

Love it, we are already doing that with our Lambdas - cause why not use the vCores when you got them 😍

I have had hours long lectures in college level programming classes on the differences between concurrency and parallelism and the first 3 minutes of this video did a better job of explaining it. Shout outs to my bois running the us education system for wasting my money and my time 💀

seeing my cpu throttle and core usage rise in realtime was impresive :)

Just brilliant

each value should be a random value, and you should sum them in the end to ensure the compiler / interpreter does not optimize all the work away because it detected that you never used the values

man i been wanting something about workers for so long

I did use this back in 2018. I don't know how much it improved, but error handling was painful. Also, when you call postMessage(), v8 will serialize your message, meaning big payloads will kill any advantage you want. And also, remember that functions are not serializable. On the UI, I completely killed my ThreeJS app in production when I tried to offload some of its work to other threads :D Apart from that, you should NEVER share data between threads, that's an anti-pattern.

Fireship, the "S" sounds in your video sound really harsh. Consider using a de-esser plugin or a regular compressor plugin and your stuff will sound fantastic. Cheers.

I just recently experimented with the Offscreen Canvas handling rendering on a separate worker thread. Pretty cool.

Awesome video ending

Woulda been cool if you set it to show core usage on taskmgr

Spawning workers in Node is not new, but support for web workers in browsers is comparatively new. Good shit man.

No clue if this could be an interesting video, but teach us about how to deploy on different environment ( ex: testing, production), as a junior i always don't know what this implies. Also show us tools to handle it. Thanks :)

with the amount of time I've spent on this video because of the while loop, even the algorithm knows who my favourite youtuber is

I remember when I first learned workers, I didn’t realize k could use a separate js file so I wrote all of my code in a string, it was just a giant string that I coded with no ide help. That was fun.

A single x86 core can actually run more than one command at a time. And the n64 can run 1.5 commands at a time when it uses a branch delay slot.

love how you tell us to leave a comment if it's locked like we can even do that

Wow, Love this tick - tock snippet

I'm still amazed at how you find such accurate images as the one at 0:32 🤔

I executed the while-loop on the orange youtube and I couldn't change the volume.... Thanks.

0:15 I already know this and already using this BLOB to create new Worker and going I use max 4 to 8 as one for each core

You are a youtube genius man

UNLIMITED VIEW TIMES!! AWESOME!! What a great video!

0:31 concurrency incorporates parallelism what you should is asynchronism

I once made a volume rendering thingie with Three.JS and it really, REALLY benefited from Web Workers, especially interpolation between Z slices.

Hyperthreading generally gives a 30% bump in performance, your test demonstrated that handily.

IM STILL STUCK OVER HERE, HELP!?!?!?!? MY PC WONT SHUTDOWN, ITS BEEN 5 MONTH'S... keep up the great work, love your vid's!

In python, handling Race Condition is easy, Use Queue, and Lock 😊

Epic! It's FLAT!

What are some of the useful libraries which help or use workers? Like Partytown or Comlink

I wonder if there are things like mutex locks to help with the synchronisations of shared resources?

Elixir is faster than I thought and getting faster with the new JIT compiler improvements.

i wish you showed the CPU usage on each logical processor on task manager instead of the overview

Just in time for my new browser game🎉

I tried the while loop thing and somehow my computer became sentient. Y'all should try that out.

Mr jeff will you do one on creating a websocket server in node js?

people watching on phone: “that level of genjutsu doesn’t work on me”

Please help, I have been trapped here for 5 years, the browser still won't let me out.

mindblowing intro

I saw this video of Code with Ryan.

Ending is the moment you are glad you watched it on a mobile device

The one time I look up something, fireship uploads a video about it lol

Jeff thank you! I implemented a worked thread in my project and it's performance is unbelievable! An incredibly big for loop and data generation was 30 minutes to be finished. With worker thread it has bern reduced to just 1 second!!! Awesome!! And it was easy to implement thanks to your video and explanation!

I thought worker threads were virtual threads. you learn something new everyday!

Exactly. I don't know why I keep hearing otherwise

To do this magically in c/c++ use openmp, in rust use rayon.

Hi from Vietnam, where the kitchen image was taken.

So weird, this was an interview question yesterday.

7:40 I knew the joke coming from mile away nice one 😂😂😂😂

That trick to force us to hear the sponsor block could only come from you 🤣🤣🤣

pro tip: create a loop like this. for (let i = 0; i < 2; i++) { i--; } This will make you pass the interview no-more questions asked.

Every async thing you do goes to micro task or task queue, and every single one of them is executed on different thread, and once it’s done it goes back as message queue to micro task queue or task queue - when callstack is empty event loop takes firstly from microtask queue to callstack, later from task queue. Web workes once are done also goes to main thread to the callstack

I've used the web worker API to filter multiple arrays at once and it's okay but it is very unintuitive to use and it could definitely be improved upon. Ideally for multiple Dom manipulation at once too not just data processing.

Can you cover native threads vs green threads?

3:17 Dude the 12900k has 16 physical cores (8p+8e) and a total of 24 threads since only the p cores have hyper-threading ❗

thanks for hanging

Are there any major baseline “costs” that need to be considered when spinning up workers? (start time, considerable ram etc)? Thanks for the content.

Dude he is helarious

I recently did a little side project where I needed to use a worker in a web app. The gist of the project is given a winning lottery number, how many “quick picks” or random tickets would it take to finally hit.

That's hillarious

6:42 bro really doubled it and gave it to the next thread

JavaScript is great, rpg maker MV uses js too, so I reckon rpg maker MV is a great way to get into js, a lot less boring than web design(although web design is great, probably why I got a cert for it hahaha)

And remember, don't make promises you can't keep

Damn, now that's a hack. Though I understand that for legacy reasons proper parallelism could be a bit too hard to do but starting but just starting more processes is kind of ridiculous