Isolation of table rows on a overloaded server
I encountered a problem when deploying the application to a server with high load. The application runs smoothly and without problems on localhost. However, when deployed to a server with high load, it is very slow, and apart from the speed, there are other issues as well.
When I click on the edit action of a row in the table, the edit action often opens empty or contains a record from the adjacent row. It is also annoying that when I click on the action on multiple rows, the previous ones are not canceled, but it tries to run all of them and ultimately opens the first one anyway.
Is there any way to solve this lack of isolation of individual table rows?
1 Reply
This is probably happening because of the stat widget on that page, where I have a running time that refreshes every second, and the update events are causing confusion. Do you know how to refresh the stat component effectively? Or would it be better to create a custom widget that refreshes itself in some other way?