Mule 4 Thread Management on CloudHub | MuleSoft Tutorial

Подписаться 3,1 тыс.

Просмотров 5 тыс.

50% 1

In MuleSoft's runtime version 4 the execution engine was replaced. This video explains the new threading strategy. Threads are now grouped into pools named CPU Light, CPU Intensive, and IO,(CPU_INTENSIVE, CPU_LITE, BLOCKING_IO). Knowing the number of threads in each pool and how they are allocated is very important in creating effective and efficient Mule applications. Especially when deploying them to CloudHub's server environment where server resources are limited.
Links in video:
blogs.mulesoft... docs.mulesoft....
Disclaimer: Described in this video is how the Mule Runtime Engine operates on versions 4.0, 4.1 and 4.2. There have been rumors that in 4.3 there might be some changes coming in. Stay tuned for more video updates.
FOLLOW ME ON SOCIAL MEDIA
LinkedIn: / jasonestevan
Twitter: / jasonestevan

Опубликовано:

21 окт 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 21

@sivathankamanee-channel 4 года назад

Excellent and Useful Topic, Jason. These are the topics that are hard to get googling or going through technical documentation makes difficult. Your explanation is very helpful and made the understanding easy. Thanks for this video.

@JasonEstevan 4 года назад

Most of my video topics do come from issues I've had in my work experience. I just wish I could make them as frequently as you ;)

@moronicintelligence6761 4 года назад

Siva, your videos are very useful.

@ashishkhkh 4 года назад

Explanation is absolutely fantastic.

@RamKrishna-vm3mp 4 года назад

Great video on internals of thread pools. Thank you very much.

@Harikrishna-ie4um 4 года назад

Loved it. Understanding mule docs is difficult for these type of topics.

@AZeeee 4 года назад

Well done Jason. Very insightful. !!

@snehak9176 4 года назад

Very Useful! I did face these issues, thanks for clearing the confusion!

@mikebackhouse9129 4 года назад

What a find! Great video. So for Cloudhub, as a rule of thumb determine max number of threads in the most thread intensive component for each flow? Then I wonder if these props could be linked via calculations based on vCore sizing etc, so any scaling (auto or manual) can be done seamlessly , without the opps team having to do another manual step?

@Saikumarsunny12 6 месяцев назад

Good explanation 🎉

@nitishjain4218 4 года назад

Thank You for the Video. Very well explained. Max concurrency to be set for 4 everytime? And in case of batch processing??

@JasonEstevan 4 года назад

Hi Nitish, it will depend on other factors too. For example your flow might not be as Dataweave intensive as mine. But now you will understand what to look for. Batch processing would probably need another video...

@nitishjain4218 4 года назад

@@JasonEstevan Thanks!! Next Video Awaited.

@rohitkarkera001 4 года назад

Very well explained :) Thank you. I was wondering how was CPU utilization behaving after making the max concurrency set to 4? and did we achieved the time difference? And in case of multiple and heavy files is it recommended to increase the vcores? is it recommended to change the processingType for dw? Last but not least please upload videos frequently :P

@JasonEstevan 4 года назад

Thanks Rohit. The file processing times went back to 69 seconds with the max concurrency set to 4. The CPU utilization still shows usage but if we ran these jobs for longer you would see the un-throttled app crash at 100% usage and the throttled app as a flat line forever. I would always try to configure your application within MuleSoft first before you solve the issue by increasing the vcores. Your manager will thank you for saving them money :)

@prakashsaurabh1020 4 года назад

Nice Explanations

@nemanjavajagic8703 4 года назад

Man, could you please do an updated version of Upsert clip you did a while ago last year. I am doing a project for college and i cant figure out how set the choice router :(