🚀 Feature: don't upload the whole document when editing only one field

[t0mm4rx]

🔖 Feature description

Hello,

I'm working with large datasets. I noticed that it takes me 10s of seconds to change a single text field of a document.
By inspecting the network call I noticed that the Console uploaded the whole document when clicking on the "update" field.
The more data I get the slower the Console becomes.

It could be a great (and quick to implement) improvement to only update the field that was actually edited.

In my case, the collection has a relationship array, containing multiple MBs of nested data.

🎤 Pitch

It would considerably improve the user experience while working with big databases.

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[joeyouss]

Thank you so much for your feedback. Our team will look into this problem to understand what best performance optimizations can be made here.

[joeyouss]

Hi @t0mm4rx

Following up on this with you, I would love to know which part is causing the speed to decrease. Can you help me with anyn details you might have about approx time it takes to list documents, update only one attribute and to create a normal request? Or any other part which is actually slow?
I ask this since then it would be easier to spot where the problem lies and we can work on the slow part.

[t0mm4rx]

Hi @joeyouss ,

I noticed two main performance issues concerning the Console:

• When listing a collection (clicking on the collection name on the sidebar), it also loads all the collection relationships. I have a collection of 20k documents, and every document has about 100 relationships inside of them. It makes the UI super slow and irresponsive as it fetches everything. A suggestion would be to only load the IDs of the relationship and to load the actual document on the mouse hover, or when clicking the ID for example.
• When updating a single field in the data tab of a document, the whole document is sent back to the API. It's very slow as it might also update hundreds of relationships for nothing. A suggestion would be to only update the field that has been updated. It's very easy to implement as each field has its own Update button. Every button could send a PATCH call only to its associated field.

Let me know if that answers your question.