Current filter:
                                You should refresh the page.
                                  • in BI when the result has many records the chrome consumes a lot of ram memory, there is the possibility of getting the BI grid paginated to minimize the amount of records that are displayed and therefore the consumption of ram which encourages the user's pc very much? 

                                • Constant (DevExpress Support) 10.10.2019

                                  Would you please clarify what memory allocation you see on your web site? In my test project, it requires about 150Mb of memory to display a grid item with 7 dimensions, 6 measures, and 50.000 rows of data. The grid widget uses the paging feature by default. Most of this memory is required to store actual data received from the server side and scripts/objects required to display this data.
                                  If you see a different result in your application, please provide us with snapshots demonstrating the memory allocated by the clear dashboard control and the memory allocated after loading the problematic dashboard. In addition, please provide the actual dashboard XML file.
                                  We look forward to hearing from you.
                                  As an immediate solution, try enabling LimitVisibleDataMode to avoid displaying huge amounts of data.

                                • Customer84242 10.11.2019

                                  screen shot of the memory 

                                • Customer84242 10.11.2019

                                  actual xml 

                                • Constant (DevExpress Support) 10.11.2019

                                  Would you please make memory snapshots using Chrome Developer tools and clarify what is your data source size and the size of displayed items?

                                • Customer84242 10.11.2019


                                  This is the memory snapshot
                                  Best regard

                                1 Solution

                                Creation Date Importance Sort by

                                Thank you for your update. Your snapshot demonstrates that most part of memory is required to store items' data on the client side. By default, the dashboard displays only the grid item and a few filter elements on the first tab page. However, it requests data for all items even if they are placed in hidden tabs. Thus, there are two ways to decrease the amount of memory required by the dashboard:

                                1. Simplify the actual dashboard layout to limit the number of items placed in the hidden tabs. The sample project provided in the How to filter one dashboard using parameters based on the data selected in another dashboard example demonstrates how to use one dashboard to set a filter and use this information to filter another dashboard. You will need to define multiple different dashboards instead of multiple tabs in the same dashboard and limit the number of dashboards displayed at once.
                                2. Set the default filter for the filter elements to avoid displaying all data on the first load. Please refer to the Manage Dashboard State help topic describing how to set the default state to set the default filter for filter elements.

                                We are ready to research what also can be done to decrease the amount of memory required to display that dashboard. However, we need to replicate the problem on our side first. A sample project demonstrating the issue including the required data source backup file will be very helpful.