Current filter:
                                You should refresh the page.
                                  • Hi,

                                    We are using the reportdesigner in our web application.
                                    After we upgraded from version 18.1.6 to 19.1.6 we experience performance issues using the reportdesigner with a large context.
                                    I have included a test project with an example and a video where you can see that memory consumption of chrome browser is increasing very fast.
                                    It seems to happen when navigating the datasource and selecting the datamembers.

                                    Kind Regards,
                                    Martijn Gertsen

                                • Vasily (DevExpress Support) 10.04.2019

                                  Hi Martijn,
                                   
                                  I assume that this issue is caused by the fact that in earlier versions the Field List items were loaded only when the field list item was expanded. And in the latest versions to improve the user experience we pre-load the next field list level once the field list is expanded. This is done to speed up the field list items expansion for end-users. So, now when the "TestContext1" item is expanded, not only its data items are loaded, but also all inner data items that increase memory usage.
                                   
                                  In any case, would you please elaborate on why your model has so many data items in your real-life application? Also please clarify what data source component is used in your real-life application.

                                • Martijn Gertsen 10.04.2019

                                  Hi,

                                  We are using the exact same situation in our real life application as in the example project.
                                  This means we use the EFDataSource with a model of 300+ entitties.
                                  A lot of models have references (relations) to each other and even self-references (parent to child for example).

                                  The reason we use such a large datasource is because we want our customers to be able to design their own reports based on our full application data.
                                  In our opinion it was working quite well before, but as of version 19.1 it does not seem like an user-experience improvement in our case.
                                  The browser is eventually becoming unresponsive when designing a report.

                                • Vasily (DevExpress Support) 10.07.2019

                                  Hi Martijn,

                                  Thank you for your clarification. Now I see your point. I discussed this situation with our development team and we decided to research the possibility of providing an option that will enable old data loading behavior in the designer's Field List element. We need some additional time for this. We will update this thread once we make any progress in this regard. Please bear with us.

                                1 Solution

                                Creation Date Importance Sort by

                                Fixed:


                                Additional information:

                                With this fix, we provided the client-side DevExpress.Analytics.Widgets.TreeList.LoadChildItemsForCollapsedNodes option. Disable this option in the client-side code when the Web Report Designer is initialized to avoid loading fields for collapsed items of the Field List.

                                As a side effect, after disabling this option, the expand buttons will be displayed for all data sources and collections in the Field List (even if this data source / collection does not have inner fields).

                                Show all comments
                                • Martijn Gertsen 12.13.2019

                                  Hi,

                                  I have been testing the fix with the previously uploaded example, but I still experience slow datasource navigation in several screen s off the reportdesigner.
                                  Also memory usage in the chrome browser is much higher then it was before (for example in version v18.2.10 ).
                                  Although the EntityFramework datasource has about 350+ entities, this should not lead to more then 1,5GB memory consumption in the browser (with v18.2.10 only 500Mb is used).

                                  I noticed that the same issue also seems to occur in the dashboard tool. When selecting the datasource for a filter it takes about 30 seconds before the items are being showed. Again I believe that this is too much time for loading a list of 350 items.
                                  I have also tried decreasing the number of dbset properties on the EntityFramework dbcontext, but that does not seem to help reducing memory or speed up the navigation.

                                  Best regards,
                                  Martijn

                                • Vasily (DevExpress Support) 12.13.2019

                                  Hi Martijn,

                                  I have tested this fix on my side on the sample project that you sent us earlier (I used 19.2.4 build) and I was not able to replicate this issue anymore. Check the attached video for more details. So, would you please elaborate what code you used to disable the DevExpress.Analytics.Widgets.TreeList.LoadChildItemsForCollapsedNodes option on your side? Or maybe I missed some steps that were required to replicate this issue?

                                  Note that disabling this option should also affect the dashboard components on your web page.

                                • Martijn Gertsen 12.13.2019

                                  Upon the end of your video is when the memory consumption will increase.
                                  Setting the argument data member of the series adding another series and setting the argument data member of that one as well.
                                  Then switching between chart and series settings will increase memory and make it unresponsive.
                                  Please check my video. After 1 minute you will see the memory increasing to more then 1.5GB. 

                                • Martijn Gertsen 12.14.2019

                                  I have also created 2 video's regarding Dashboard grid datasource selection where you can see that responsiveness in version 18.2.10 is much better then in 19.2.4.
                                  This is just an example, but gives an expression of the overall responsiveness decrease which we experience with 19.2.4. 

                                • Vasily (DevExpress Support) 12.16.2019

                                  Hi,

                                  Thank you for your update. We need some additional time to compare our Web Report Designer component's performance and memory usage in 18.2.10 and 19.2.4 versions and research this issue if we find the difference. We will update this thread once we make any progress in our research. Please bear with us.

                                  As for your dashboard related question, I have extracted it to a separate ticket created on your behalf, to avoid discussing multiple topics in this thread, T846026: Dashboard grid datasource selection performance decreased after upgrade to 19.2. Let's continue the conversation regarding the dashboard components performance in that thread.

                                • Vasily (DevExpress Support) 12.19.2019

                                  Hi Martijn,

                                  Thank you for your patience. We have researched the issue demonstrated on your video by testing this scenario by using versions 18.2.10 and 19.2.4. After peforming this research we found that the memory consumption grows in 19.2 version after the root item is selected on the Chart Structure panel of the Chart Designer. And when you select any other item on this panel the memory is released back (you need to wait 1-2 minutes until the browser clears the garbage ). So, I have created a separate ticket for this issue and forwarded it to our developers team for the further research: Web Report Designer - Chart Designer's memory consumption increased after upgrading to version 19.2. We will update that ticket once we make any progress on this issue.

                                  As for the other steps demonstrated on your video, I see that the memory consumption is nearly the same in versions 18.2 and 19.2. So, I assume that the main problem here is with the Chart Designer. In any case, if you see any other differences between these versions' memory consumption please report these issues to us so that we will be able to test these scenarios on our side. By the way, I have attached the sample projects that we were using on our side to compare the memory consumption of the aforementioned versions.