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
You know, it's a real shame that we put all this time and effort into being able to lazily deserialize objects, and not have lazy serialization back out. I know, it's a bit more complex than that - but, is it really? Couldn't we just do a direct 1:1 copy in/out of memory to some storage cache?
I realize there are things this may not work for, but what could it work with? We have options here people! But we may need to kinda figure out what those options are and what they could look like, and what kinds of savings we could get.
If we could do this though, and the savings were worth it, we might be able to get away with much MUCH larger systems on even the smaller MCU setups, and might actually wind up dropping our memory usage to reopen smaller devices into the working category. It's a long shot, but theoretically possible. Would be worth at least some sort of investigation and costing.
The text was updated successfully, but these errors were encountered:
NachtRaveVL
changed the title
Investigate: Unloaded unused objects to limit memory
TODO: Object unresolving/caching to reduce memory footprint
Feb 11, 2023
You know, it's a real shame that we put all this time and effort into being able to lazily deserialize objects, and not have lazy serialization back out. I know, it's a bit more complex than that - but, is it really? Couldn't we just do a direct 1:1 copy in/out of memory to some storage cache?
I realize there are things this may not work for, but what could it work with? We have options here people! But we may need to kinda figure out what those options are and what they could look like, and what kinds of savings we could get.
If we could do this though, and the savings were worth it, we might be able to get away with much MUCH larger systems on even the smaller MCU setups, and might actually wind up dropping our memory usage to reopen smaller devices into the working category. It's a long shot, but theoretically possible. Would be worth at least some sort of investigation and costing.
The text was updated successfully, but these errors were encountered: