Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grid - Performance issue in an Angular CLI application #551

Closed
rsharmapinnakl opened this issue May 11, 2017 · 2 comments
Closed

Grid - Performance issue in an Angular CLI application #551

rsharmapinnakl opened this issue May 11, 2017 · 2 comments

Comments

@rsharmapinnakl
Copy link

@rsharmapinnakl rsharmapinnakl commented May 11, 2017

I have been upgrading my application from AngularJS to Angular(v4). I created my Angular application using the Angular CLI. I noticed that the Grid becomes very slow(on scrollling, sorting etc.) when there are a significant number of rows(>100). This was never a problem with kendo UI for AngularJS.

Also, when I tested this on a Kendo plunker, the grid performed well, though not as good as the grid for AngularJS or jQuery.

Here's a minimal Angular CLI project using the kendo grid for around 500 rows- https://github.com/rsharmapinnakl/angular-kendo-grid-example

Here's the same code on a plunker - http://plnkr.co/edit/zhegT2?p=preview

I don't understand why these two perform differently. The grid in the Angular CLI project does not provide an acceptable user experience. Is there a way to fix this?

@rkonstantinov
Copy link

@rkonstantinov rkonstantinov commented May 11, 2017

You should make sure that the app is running in production mode by starting it with ng serve --prod

@tsvetomir
Copy link
Member

@tsvetomir tsvetomir commented May 26, 2017

For Angular CLI projects append the --env=prod flag, e.g. ng build --env=prod

Closing this issue, but feel free to reopen if you identify any specific performance problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.