You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is to optimise the loading speed, but also to choose dynamically other type of Data to be in the heap ( of course we keep the blog structure in heap memory )
Since the website structure might not use all the heap memory, the idea would be to have a third option : ephemeral in the list of ( Heap, Stable, ephemeral ) to use what is left of the heap memory for often used data ( popular or recent stuff ).
While "Popular" might quite be complicated to judge, "Recent" stuff would be quite easy to spot using just the timestamp of the collections. My suggestion is that for every satellite, we calculate the memory left from the heap for collection that are the most recents.
PROS :
It wouldnt change much for a website like juno.build, but for a blog giving regular news, that would allow the new collections, and the overal page, to load faster and cheaper. - Without manually change the data storage by hand -
CONS :
New feature induce dev costs/time.
Difficulty to see if a regular check of memory state would not add superior extra cost.
Difficulty to see if the change of heap to stable memory wouldn't also add extra cost.
This ephemeral boolean option should be coded when we setDocs, so we do not need to manually go to the satellite UI.
Tell me what you think about it, it is also hard to know how slow the stsable memory is to judge if this is really necessary.
Cheers and keep the great work David 👍 !
The text was updated successfully, but these errors were encountered:
The idea is to optimise the loading speed, but also to choose dynamically other type of Data to be in the heap ( of course we keep the blog structure in heap memory )
Since the website structure might not use all the heap memory, the idea would be to have a third option : ephemeral in the list of ( Heap, Stable, ephemeral ) to use what is left of the heap memory for often used data ( popular or recent stuff ).
While "Popular" might quite be complicated to judge, "Recent" stuff would be quite easy to spot using just the timestamp of the collections. My suggestion is that for every satellite, we calculate the memory left from the heap for collection that are the most recents.
PROS :
CONS :
This ephemeral boolean option should be coded when we setDocs, so we do not need to manually go to the satellite UI.
Tell me what you think about it, it is also hard to know how slow the stsable memory is to judge if this is really necessary.
Cheers and keep the great work David 👍 !
The text was updated successfully, but these errors were encountered: