Resource-heavy #362

New issue

Open

opened 2026-06-26 10:41:33 +00:00 by adina · 0 comments

adina commented

2026-06-26 10:41:33 +00:00

Owner

[This is documenting notes from this hedgedoc in order to have them as proper issues. See also: #350 ]

Resource-heavy

After editing 30-40 large-ish records, the shacl-vue tab consumes >2GB of memory.

Out of curiosity: was this before submission? And did you submit all 30-40 records afterwards simultaneously? How was that UX?

My guess is that it's not necessarily about the number of edited records themselves, but rather the amount of extra queries (for related records) that are made as a result of working with 30-40 records. Those are typically kept to a minimum, records are fetched as and when needed. I am not sure what would be a sustainable solution for this. Somehow we need to get unnecessary data out of memory in real-time. We can use persistent storage in the browser, but I don't actually know how much of a benefit that will bring, and it also opens up security concerns when working with sensitive data. I'm open for any different ideas here. I can try to determine what exactly uses most of the memory in the described scenario. [name=jsheunis]

[This is documenting notes from this hedgedoc in order to have them as proper issues. See also: #350 ] ## Resource-heavy After editing 30-40 large-ish records, the shacl-vue tab consumes >2GB of memory. > Out of curiosity: was this before submission? And did you submit all 30-40 records afterwards simultaneously? How was that UX? > > My guess is that it's not necessarily about the number of edited records themselves, but rather the amount of extra queries (for related records) that are made as a result of working with 30-40 records. Those are typically kept to a minimum, records are fetched as and when needed. I am not sure what would be a sustainable solution for this. Somehow we need to get unnecessary data out of memory in real-time. We can use persistent storage in the browser, but I don't actually know how much of a benefit that will bring, and it also opens up security concerns when working with sensitive data. I'm open for any different ideas here. I can try to determine what exactly uses most of the memory in the described scenario. [name=jsheunis]