Brilliant as usual. I'm not sure if I will have to leverage all of its potential in the near future but for sure this video is a masterpiece showing content that is not widely available in any other place. Thank you!
Another masterpiece. Thank you for sharing. Could you please share some advice on how to learn things under the hood like you do, what kind of thought process should I have when I'm learning?
Nice video. I think the image processing was so much quicker when using the worker is because Chrome's CPU throttling wasn't being applied to the worker.
Maybe yes or maybe because it is the real OS thread and can invoke more resources… Here I might be wrong because that is not the area where I am so confident :) What I wanted to say in the video is that while worker performed their work the main thread wasn't blocked and users could still interact with the application without glitches :)
Thank you so much for this incredible explanation of web workers! 🌟 Your clear and straightforward approach made a complex topic so much easier to grasp. I really appreciate the effort you put into making it accessible and engaging. Keep up the fantastic work!
I really like how you explain it. So in Angular, let's say you're using mat-table from angular material. I know a lot of people had some performance issue with it. Is it a good idea to use web-worker for a long running API requests? If yes, would web-worker solves the perfomance issue with loading thousands of rows into that mat-table component?
ปีที่แล้ว
Awesome video on web workers. I used to be so confused about them and it was hard to find well explained resources along side practical examples. Il will definitively recommand this video to my team.
Hi Dmytro, Excellent introductory video on the topic of Web Workers. I think it would have been worth stressing they are not a feature of Angular but a Web API (maybe show the MDN page). To complete the discussion it would also be worth showing how you might write a unit test/exercise a web worker. Thanks.
Thanks for sharing :) Small point - It would be useful to emphasize that the Webworker runs outside of the angular context, so there's no access to your angular context, apart from passing things through as parameters.
the 192ms in the Webworker version was just for setup. The filter took ~500ms which is the 3110ms / 6(CPU throttling) In other words, CPU throttling did not apply to the Webworker and in the end the whole thing even took a little longer because of the message passing. In the end there was no speed up but still unloading the main thread which is still a good thing. To actually get speed up you could have segmented the image into patches and fed each one to its own Webworker. This would have actually reduced total processing time if you have a multi core CPU which you most certainly do.
Really great video! I want to ask question since we moved out the implementation to the worker, how does this same method work fast in webWorker? but not in the angular context? I understand the concept of using webWorker to take care of heavy-lifting and not blocking of main-thread and that's what it is doing but how it is increasing performance.
Hello there, i have learned a lot woth your videos and Thanks a lot for that I was hoping that you could make some videos on nx workspaces it would be a great series Thanks
Thank you, Now we have how to switch context from main thread to worker and back. Can you please look into issue of browser being non-responsive when large data is loaded on the screen without using AJAX calls to get chunk of data? How do we optimize such scenario? For example, a select drop down having large options.
I would love to see and example of this, maybe build into a service, where the usage of it just being subscribing to the service that handles webworker task including listening for messages. Also to help with some stricter typing. The times i have used webworkers, its just been with basic javascript. I would like to use interfaces to make it more type "safe".
Thanks for the amazing video, just need to ask that this webworker can be used for saving the object position on the canvas like on moving event scaling event like saving there x and y cordinatiiones while performing canvas event?
Thank you for great tutorial ....I just wonder if it is possible to chain the workers to apply multi tasks in a queue and once done pass refreshing main thread? How does the communication between main and several workers works?
Ty 4 video. Hower, i have one question left. How does webworker performs it's calculation? Is it something similar to Web API or does it take a separate computer thread in that case and if so, is there a way of using webworker on single thread cpu?
I have a stupid question not specifically related to this topic. What is the advantage of providing types to the property with this operator (!:) like in the video I saw all the properties declared like private worker !: Worker. We could have provided type by worker : Worker also. So what's the reason here?
Дякую за відео! Мав досвід генерування великих пдф файлів з допомою веб воркерів. Чудово вирішували таку проблему. Памʼятаю що стикався з фактом що файл воркеру скачувався багато разів (як розумію на кожен інстанс воркера, проте не впевнений). Звідси 2 питання (не обовязково до автора, може хтось стикався): 1. Чи є ліміт на кількість воркерів для 1єї таби? 2. Якщо n інстансів воркера створюються з 1го файлу, чи дійсно це призводить до того що той самий файл фетчиться n раз? Чи можна цьому якось запобігти?
Level up your Angular skills with my advanced courses 🚀
bit.ly/advanced-angular-courses
your free contents literally better than paid courses 🎉
thats a rare case but very useful when you need it.
Where is the super like button. Great in-depth content as always
Thank you, absolutly fantastic video🙏
Thanks for good explanation, now it’s clear
Brilliant as usual. I'm not sure if I will have to leverage all of its potential in the near future but for sure this video is a masterpiece showing content that is not widely available in any other place. Thank you!
дякую за контент!!!!
Комментарий для продвижения канала, спасибо за то, что делаете. Отличный контент!!
Дякую за контент
Excellent, love the way you explane the concept
Дякуемо, Дмитро!
Great as always
Useful video, and a gorgeous cat 🐈
this video was super useful, thanks buddy
Дякую за контент, це золото
Дякую пане Буданов 😄🙌🏻
Looks like spawned worker doesn't have that "x6 slow" limitation, main thread has.
Another masterpiece. Thank you for sharing. Could you please share some advice on how to learn things under the hood like you do, what kind of thought process should I have when I'm learning?
Nice video. I think the image processing was so much quicker when using the worker is because Chrome's CPU throttling wasn't being applied to the worker.
Maybe yes or maybe because it is the real OS thread and can invoke more resources… Here I might be wrong because that is not the area where I am so confident :) What I wanted to say in the video is that while worker performed their work the main thread wasn't blocked and users could still interact with the application without glitches :)
Thank you, very comprehensible especially for use, fro pros and corns of using
Decoced Frontend, you are bang-on as always. Can we expect a tutorial on Service Worker as well?
very well explained as always. peace!
Nice video!
Thank you so much for this incredible explanation of web workers! 🌟 Your clear and straightforward approach made a complex topic so much easier to grasp. I really appreciate the effort you put into making it accessible and engaging. Keep up the fantastic work!
thanks it was very informative.
Thank you for this amazing content you create
You are welcome 😊glad you like it
I'm a total noob with web workers but it was very clear, thanks man
I really like how you explain it. So in Angular, let's say you're using mat-table from angular material. I know a lot of people had some performance issue with it. Is it a good idea to use web-worker for a long running API requests? If yes, would web-worker solves the perfomance issue with loading thousands of rows into that mat-table component?
Awesome video on web workers. I used to be so confused about them and it was hard to find well explained resources along side practical examples.
Il will definitively recommand this video to my team.
Hi Dmytro, Excellent introductory video on the topic of Web Workers. I think it would have been worth stressing they are not a feature of Angular but a Web API (maybe show the MDN page).
To complete the discussion it would also be worth showing how you might write a unit test/exercise a web worker.
Thanks.
Great to see new content from you :)
Thanks a lot, as usual everything arranged and explained
Greate video, thanks
Thanks for sharing :) Small point - It would be useful to emphasize that the Webworker runs outside of the angular context, so there's no access to your angular context, apart from passing things through as parameters.
Incredible useful! This all is based on strategy pattern, I am a Java programmer an this is very alike annotations made by Martin Odersky in Java 7
thank you! as always - rally good quality👍
Thanks for the new content!
Amazing content as always! Thank you so much, this was super helpful for me 😄
Thank you for the great video!
Thanks for another useful video, Dmytro) Very interesting and informative as usual
can you provide more content on service worker and its usecases?
the 192ms in the Webworker version was just for setup. The filter took ~500ms which is the 3110ms / 6(CPU throttling) In other words, CPU throttling did not apply to the Webworker and in the end the whole thing even took a little longer because of the message passing. In the end there was no speed up but still unloading the main thread which is still a good thing. To actually get speed up you could have segmented the image into patches and fed each one to its own Webworker. This would have actually reduced total processing time if you have a multi core CPU which you most certainly do.
For SSR provide a fallback mechanism to perform the computations that the worker would Perform.
Really great video! I want to ask question since we moved out the implementation to the worker, how does this same method work fast in webWorker? but not in the angular context? I understand the concept of using webWorker to take care of heavy-lifting and not blocking of main-thread and that's what it is doing but how it is increasing performance.
Hello there, i have learned a lot woth your videos and Thanks a lot for that
I was hoping that you could make some videos on nx workspaces it would be a great series
Thanks
Thank you,
Now we have how to switch context from main thread to worker and back.
Can you please look into issue of browser being non-responsive when large data is loaded on the screen without using AJAX calls to get chunk of data? How do we optimize such scenario? For example, a select drop down having large options.
Thanks for your question. I think the Virtual Scrolling from Angular CDK will help you.
How to use interfaces or any common types between component and webworker?
Thanks for the knowledge but do you recommend executing expensive Http services from the worker
I would love to see and example of this, maybe build into a service, where the usage of it just being subscribing to the service that handles webworker task including listening for messages. Also to help with some stricter typing. The times i have used webworkers, its just been with basic javascript. I would like to use interfaces to make it more type "safe".
Thanks for the amazing video, just need to ask that this webworker can be used for saving the object position on the canvas like on moving event scaling event like saving there x and y cordinatiiones while performing canvas event?
Thank you for great tutorial ....I just wonder if it is possible to chain the workers to apply multi tasks in a queue and once done pass refreshing main thread? How does the communication between main and several workers works?
Thanks! Learnt something new today :)
Would it be possible to efficiently wrap a large JSON array into an ArrayBuffer to avoid data duplication?
Ty 4 video. Hower, i have one question left. How does webworker performs it's calculation? Is it something similar to Web API or does it take a separate computer thread in that case and if so, is there a way of using webworker on single thread cpu?
So in a shorthand analogy JS is a Boss that does not delegate tasks to staff as long as you employ some workers and start delegating :)
0:57 is that was blink like "naaa, I'm kidding"? :D
I have a stupid question not specifically related to this topic. What is the advantage of providing types to the property with this operator (!:) like in the video I saw all the properties declared like private worker !: Worker. We could have provided type by worker : Worker also. So what's the reason here?
Дякую за відео! Мав досвід генерування великих пдф файлів з допомою веб воркерів. Чудово вирішували таку проблему.
Памʼятаю що стикався з фактом що файл воркеру скачувався багато разів (як розумію на кожен інстанс воркера, проте не впевнений). Звідси 2 питання (не обовязково до автора, може хтось стикався):
1. Чи є ліміт на кількість воркерів для 1єї таби?
2. Якщо n інстансів воркера створюються з 1го файлу, чи дійсно це призводить до того що той самий файл фетчиться n раз? Чи можна цьому якось запобігти?
A CAT on the couch!!!!!!!!!!!
Спасибо!
SSR has its own workers
спасибо за контент, было интересно
вопрос: есть ли на канале может видео про то какие полезные плагины для Ангуляра ты используешь в своей ide-шке?
Maybe try to speak a different language, at least while the war is not over.
@@eoz maybe u should delete video about Saint Petersburg from yr channel first, hypocrite)
I was thinking about sharing this video with teammates, but it so OP that I've decided to be first it team, who will use the worker 😈
Please make video on indexdb that is available on chrome or Firefox browser