Hi, it could be the client-side browser taking some time to render such large amounts of data. You can check in your browser developer tool to check this (for example for Google Chrome https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/timeline-tool). It is not a good idea to display so much data in the UI in one page for usability and performance reasons. Perhaps you will want to consider restructuring your UI e.g. display the data in a datalist to utilise paging.

Dear Anders,

Understand your point of view. but there only have advance Grid got the features of Inline Editing, So I have no other options for OOTB. However, is it any reason behind that the Advance Grid(pqGrid) need to duplicate the data for 3 times? And pq-Grid should able to support data paging and it should no need to load all the record in once, as I set the grid on display 20 rows per page. Anyway how I can enable this feature?

Best Regards

Tony Chu

Probably it is slow on the data loading part at the database side. Try to enable or monitor your slow query and see where you can optimize. Particularly, if there's parent-child tables involved, then you can check and add the necessary index to improve query speed.

the performance of loading the grid from the database is acceptable which is just only around 1 sec.

Hi

Good news! After months of intensive development, we're proud to announce the beta for Joget Workflow Version 6 is now available for download at http://www.joget.org/joget-workflow-v6/#next

Read what's new in Joget workflow Version 6 at http://www.joget.org/joget-workflow-v6/