This is a migrated thread and some comments may be shown as answers.

Memory requirement went from 2G to 4G

6 Answers 172 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Angel
Top achievements
Rank 1
Angel asked on 17 Mar 2020, 01:39 AM

Hi there

We are a small startup and like Kendo UI for Angular8 Datagrid very much. We downloaded a free trial to make sure it;s working before buying a license.

https://www.telerik.com/kendo-angular-ui/components/grid/how-to/filter-all-columns/

We asked a  contractor to integrate the component and he did integrate the data-grid and it looks good. But our memory requirement went from 2G to 4G and he asked us do following:

EXPORT NODE_OPTIONS=--max_old_space_size=4096

 

This is not good as we want our application to be light weight. We are almost (sadly) thinking of dropping this and looking for alternative data-grid products.

 

Could you please suggest if Kendo's angular8 has this memory expectation or we are doing something wrong?

 

Thank you so much

Angel

 

6 Answers, 1 is accepted

Sort by
0
T. Tsonev
Telerik team
answered on 17 Mar 2020, 06:12 AM

Hi Angel,

The build process of a typical Angular CLI application could be quite demanding. It gets worse as the application grows bigger and includes more libraries.

That doesn't mean that the application itself would require more memory. Much of the build resources are spent on optimizing the application and dropping unused code in the final bundle.

We, as a component vendor, don't have direct control over the build process. That said, we have a few tips for speeding it up:

* Use pre-built CSS files for the themes—either stock or customized, see Customizing Themes. Referencing the SCSS files directly puts a lot of strain on the build.
* Load only the component modules that are in use. Even if a module is unused, it remains part of the application bundle until the very last moment.

We'd appreciate any further details about your project setup if you're still experiencing issues.

Best Regards,
T. Tsonev
Progress Telerik

Get quickly onboarded and successful with your Telerik and Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
0
Angel
Top achievements
Rank 1
answered on 17 Mar 2020, 09:09 PM

Thank you so much for your reply. We just need "Data-grid" which requires following components to be loaded

"@progress/kendo-angular-buttons": "^5.2.3",
"@progress/kendo-angular-charts": "^4.1.3",
"@progress/kendo-angular-common": "^1.2.2",
"@progress/kendo-angular-dateinputs": "^4.2.2",
"@progress/kendo-angular-dropdowns": "^4.2.5",
"@progress/kendo-angular-excel-export": "^3.1.3",
"@progress/kendo-angular-grid": "^4.6.4",
"@progress/kendo-angular-inputs": "^6.5.0",
"@progress/kendo-angular-intl": "^2.0.1",
"@progress/kendo-angular-l10n": "^2.0.1",
"@progress/kendo-angular-pdf-export": "^2.0.3",
"@progress/kendo-angular-popup": "^3.0.5",
"@progress/kendo-data-query": "^1.5.2",
"@progress/kendo-drawing": "^1.6.0",
"@progress/kendo-theme-default": "^4.12.2",

 

This is coming to about 0.5G of runtime (not build time) memory. In other words, when I do "npm start" I need to increase "EXPORT NODE_OPTIONS=--max_old_space_size"

Can you please confirm:
1) Does all these components need 0.5G memory for anugular8?
2) if not, what we might be doing wrong?

If answer to (1) is yes, we can't proceed this route and would have to look for alternative product.

Thank you so much and hoping we can find a solution as we really like your data-grid.

Angel

0
T. Tsonev
Telerik team
answered on 18 Mar 2020, 01:04 PM

Hi Angel,

Can you please copy the output from "ng --version"?

The default project configuration should not require tweaking with NodeJS options to run.

Best Regards,
T. Tsonev
Progress Telerik

Get quickly onboarded and successful with your Telerik and Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
0
Angel
Top achievements
Rank 1
answered on 18 Mar 2020, 02:33 PM
ng --version
Your global Angular CLI version (8.3.24) is greater than your local
version (8.3.20). The local Angular CLI version is used.


To disable this warning use "ng config -g cli.warnings.versionMismatch false".


     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / â–ł \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/



Angular CLI: 8.3.20
Node: 13.7.0
OS: darwin x64
Angular: 8.0.3
... common, compiler, compiler-cli, core, platform-browser
... platform-browser-dynamic, router


Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.803.20
@angular-devkit/build-angular     0.803.20
@angular-devkit/build-optimizer   0.803.20
@angular-devkit/build-webpack     0.803.20
@angular-devkit/core              8.3.20
@angular-devkit/schematics        8.3.20
@angular/animations               8.2.14
@angular/cdk                      8.2.3
@angular/cli                      8.3.20
@angular/flex-layout              8.0.0-beta.27
@angular/forms                    8.1.3
@angular/http                     7.2.15
@angular/language-service         8.2.14
@angular/material                 8.2.3
@ngtools/webpack                  8.3.20
@schematics/angular               8.3.20
@schematics/update                0.803.20
rxjs                              6.5.3
typescript                        3.4.5
webpack                           4.39.2
0
Angel
Top achievements
Rank 1
answered on 19 Mar 2020, 04:12 AM

I posted the version. But apart from that can you please confirm by loading these components locally to see if these indeed take 0.5G memory.

We need to make a decision on this product or competitor product. So your quick help will be appreciated. We like your product but memory requirement is high unless there is something we are doing wrong.

 

Thanks

Angel

0
T. Tsonev
Telerik team
answered on 19 Mar 2020, 07:08 AM

Hi Angel,

I've set up a blank application that matches your environment and includes the Kendo UI Grid, see attachment. It does not require increasing the NodeJS heap size to run and build.

The problem does not seem to be caused by a specific library, but by the cumulative application and library size. It makes sense for larger applications to require more memory to run. Issue #13734 in the Angular CLI bug tracker confirms this.

This makes it likely to run into the same issue as your application grows larger and references more libraries. Consider this when taking your decision.

Best Regards,
T. Tsonev
Progress Telerik

Get quickly onboarded and successful with your Telerik and Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Tags
General Discussions
Asked by
Angel
Top achievements
Rank 1
Answers by
T. Tsonev
Telerik team
Angel
Top achievements
Rank 1
Share this question
or