I would think that they already do what you are aiming for, having a list of what is the content of the cache, opposed to a list of what can be cached. In fact, they need to record a bit more than just the block number, such as when was the block last used (timestamp) etc. etc.
But I am with you: An optimized memory model would be helpful to increase e.g. the size of the cache itself. I for instance want to enable caches larger then 2 TByte in size by using bigger SSDs. Right now its limited to less then 2 TByte in size.
An idea for getting rid of RAM overhead
-
- Level 9
- Posts: 180
- Joined: Thu Feb 03, 2011 3:22 pm
Re: An idea for getting rid of RAM overhead
Just do what dhonn suggested and have it sorted once and for all. EliteBytes Velo thing has nearly no overhead at all so it's definitely possible.