☝️Small business or a startup? See if you qualify for our special offer.
+

expanding/collapsing rows

Answered
taehong asked on September 4, 2025

I'm using Flexmonster with a custom API to display data on the screen. When there are hundreds of thousands of rows visible, the screen almost freezes and becomes extremely slow when expanding/collapsing rows in both classic and flat forms - to the point where it's unusable. Are there any ways to solve this performance issue?

9 answers

Public
Solomiia Andrusiv Solomiia Andrusiv Flexmonster September 4, 2025

Hello, Taehong!

Thank you for reaching out to us.

As a first step, we would like to know more details about the case:

  1. The approximate data size(e.g. in Mb)
  2. The characteristics of the machine where the slow data load is experienced
  3. If you are using expandAllData() API call
  4. You've mentioned "expanding/collapsing rows in the flat form" - please provide more details about this part
  5. If it's possible to provide us with access to the page so we can test it on our side, it would also be very helpful

With this information, we'll be able to advise you better.

Looking forward to hearing from you.

Kind regards,
Solomiia

Public
taehong September 8, 2025

1. The custom API (select API) returns data with a size of 159MB.

2. The machine I am using is a MacBook Pro 14 with 36GB of memory.

3. I am only using the following configuration:

slice: {
columns: [],
rows: [],
measures: [],
expands: {
expandAll: true,
},
},

 

4. I tried to attach the video, but I received a "The following files is not allowed" message. If you could provide your email address, I can send the video to you via email.

 

5. Since this is an internal company project, it is not possible to provide access to the page.

Public
Solomiia Andrusiv Solomiia Andrusiv Flexmonster September 8, 2025

Hello, Taehong!

Thank you for getting back to us and for providing the details about the case.

As a first step in investigating the case, we recommend disabling expandAll and checking whether the component works without freezing in this case. Another approach is to debug the case using a smaller portion of the dataset, then gradually increase the data size to identify the bottleneck.

The video of the case would still be a great help. Our Customer Service Manager has already sent you an email, so please check your inbox and provide the video and other attachments in response to the letter.

Looking forward to hearing from you.

Kind regards,
Solomiia

Public
taehong September 9, 2025

I have sent the video as an email attachment.

 

Also, I need to use expandAll set to True by default. When the dataset is small, the performance is a bit slow but still usable. However, with a large dataset (around 400,000 records), the component becomes too slow to use. It seems that rendering is extremely slow when collapsing or expanding. Could you please check and advise on this issue?

 

Thank you.

Public
Solomiia Andrusiv Solomiia Andrusiv Flexmonster September 9, 2025

Hello, Taehong!

Thank you for providing the video.

Based on the video, we can see that the described slow behavior while expanding is not caused by the client-side rendering. The “Loading data” popup shows that the client is waiting for a server response, and the Network tab confirms that the request stays in “pending” and “loading” status for some time before Flexmonster gets the response from the server and updates the view.

The server may be taking longer to respond, as the /select with expandAll: true for an 8-level hierarchy is quite a complex request.
As a first step in investigating the case, our team recommends looking for bottlenecks on the server by gradually increasing the hierarchy depth from 2 to 8 levels to identify where the slowdown starts.

Hope you will find our answer helpful. Please let us know if you have any further questions.

Kind regards,
Solomiia

Public
taehong September 10, 2025

Hello,

 

As you can see in the video, when collapsing, there is no server request, but the screen does not render immediately. Instead, it freezes for a moment before updating.

 

When expanding, it only takes 2 seconds to receive a response from the server.
However, rendering the updated view on the screen is noticeably slow.

 

Given these observations, I suspect that the slow performance may be related to Flexmonster’s rendering process.
Could you please check this again?

 

Thank you.

Public
Solomiia Andrusiv Solomiia Andrusiv Flexmonster September 10, 2025

Hello, Taehong!

Thank you for your swift response.

Please find our comments on the expanding&collapsing behavior shown on the provided video below:

  • First expand at 00:08
    The communication process after the expand is clicked takes 26 seconds - from 00:08 when the expand was clicked, to 00:34 when Flexmonster received the data and immediately renders it. In the Network tab, it is shown that the response time was 2.58s, but in the video, we can see that the request was in pending status for ~ 25 seconds.
    Our team strongly recommends addressing this issue on your side in order to achieve better performance.
  • Collapse on the nested node at 00:40
    We have reproduced the behavior shown on collapse at 00:40 of the video on our side. Our team will research possible solutions and get back to you with the research results with ETA September 29th.

We believe that addressing the above two cases will improve the performance. Our team also suggests shortening the nested levels where possible.

Please let us know if you have any further questions.

Kind regards,
Solomiia

Public
taehong 4 days ago

When expanding, after receiving a server response (i.e., not in the “pending” state), the screen remains in a “loading data” state for several tens of seconds before rendering.

This is different from the issue I previously mentioned, where a delayed server response causes the screen to load slowly.

I will attach the relevant information via email for your review. Thank you.

Public
Solomiia Andrusiv Solomiia Andrusiv Flexmonster 4 days ago

Hello, Taehong!

Thank you for getting back to us and for providing additional details about the case.

We think that the provided use cases can be connected, so our Dev team will take a look at both expanding and collapsing behavior within the scope of the discussed research.

The research results will be shared with you by September 29th, as agreed.

Kind regards,
Solomiia

Please login or Register to Submit Answer