Kendo upgrade to v16 become unacceptable slow

[Levon]

Upgrading Kendo packages from v15 to v16 I faced slowness during build process.
with Angular v17, Kendo v15 build takes 8min, same project with Angular v18 and Kendo v16 takes 14 min. 

Also the "Webpack Bundle Analyzer" show biggest bundle.

 

 Is there reason of slow build and huge bundle? 

[Zornitsa]

Hi Levon,

Based on the provided information, it is hard to determine what exactly may be causing the slow build process and the large bundle size that is experienced in your application. 

In this line of thought, what I can suggest at present is verifying that all installed Kendo UI for Angular packages and the Kendo Themes are updated to their latest versions. This will ensure the best possible performance with no discrepancies or dependency conflicts, and in turn, you can then see whether this will improve the build process:

• https://www.telerik.com/kendo-angular-ui/components/installation/up-to-date/#toc-updating-to-latest-versions 

Furthermore, for testing purposes, you could try stripping out the utilized Kendo components throughout your application to determine whether the build behavior is produced by our library particularly or if there is any other external cause. 

With the above being said, providing an isolated runnable project, in which we can observe the explained behavior of the build process on our side will be very helpful in the actual troubleshooting of the explained issue. In that way, we can test and debug the build process to find out whether the issue is caused by the Kendo packages and thus provide more valuable assistance on the matter.

Lastly, I want to mention that all Kendo components have their own dependencies that are needed to run the corresponding components properly, which may be a possible cause for a larger bundle size. On that note, if the dependencies are the reason for the experienced build behavior or if the cause is external, this means that on our side there is not much that can be done. So, in this case, Angular bundle size optimizations might need to be taken into consideration.

For further reference, please check any of the following articles:

• https://angular.io/guide/deployment#production-optimizations
• https://indepth.dev/posts/1217/how-to-reuse-common-layouts-in-angular-using-router
  
• https://blog.angular.io/with-best-practices-from-the-start-d64881a16de8

I hope this helps. 

Regards,
Zornitsa
Progress Telerik