I’m curious: trying to understand fibery’s impact on my RAM/swap: how much of my fibery workspace is stored in my browser’s memory while I’m interacting with it? Is the entire workspace (all Databases) resident in memory? Or is it fetching Databases/Views as necessary from the server? And especially wrt. attachments: are those all fetched and in-memory the whole time, or are they stored on the server and only fetched when viewed?
Thanks!
Hi!
Fibery frontend loads in memory everything user touch and keep track after it with comet technology.
especially wrt. attachments: are those all fetched and in-memory the whole time, or are they stored on the server and only fetched when viewed?
Generally attachment just keep the link to a file. But for images we load them as backgrounds without any size optimizations. Actually this can be painful in case of a big files (to our shame)…
Do you fill some notable memory consumption? Can you describe your case a bit?
Not much people complained about this before but there is a chance we miss something important.
Thanks for that: I have noticed that fibery seems to get slower and slower as I add more and more data to my workspace; was just trying to figure out if there are certain types of data that might be impacting the app, or Chrome’s memory usage as a whole: I have added quite a lot of images in rich text fields; I gather that will increase the app’s memory footprint: might the presence of multiple images cause the app to slow down (irrespective of running up against memory/swap limitations)?