Reports unresponsive

[jcardus]

The reports components are re-rendered each time we receive a message in the websocket.

The report page becomes very unresponsive if we generate a report with hundreds of rows (like route report) and we have enough devices on the user to receive updates frequently.

One possible solution to avoid the page from being unresponsive would be to pause the websocket in the reports page and resume when we go back to the map.

Any ideas?

[tananaev]

Why is it re-rendered?

[jcardus]

probably because of the devices dependency from the state

[tananaev]

I guess it makes sense, but it practice it's shouldn't be a problem because nothing really change on the page. What exactly is causing the unresponsiveness? How many records do you have in the report?

[jcardus]

What's causing the unresponsiveness is the re-rendering. It's not only related to the number of records, it's about number of records / number of devices in the user.

One example, 100 devices in the user, a report with 700 records.

[tananaev]

Only device status is updated live. Maybe we can separate device status into its own store. That way it shouldn't be re-rendered.

[jcardus]

You mean something like creating a deviceStatuses array in the store and reference it when we need it? Then the status and lastUpdate fields would be duplicated.

[tananaev]

Something like that.

[jcardus]

Wouldn't it be easier to just remove the socketcontroller from the reports page?

[tananaev]

Easier, but it means you will lose notifications.

[jcardus]

Ok, we can put a parameter in the controller so that when we are in reports it doesn't process devices. When we move away it would reconnect so we get the last positions / devices again.

[tananaev]

I think that's fixing the symptom, not the root cause.