forked from TrueCloudLab/neoneo-go
1c38b45074
We're paging these hashes, so we need a previous full page and a current one plus some cache for various requests. Storing 1M of hashes is 32M of memory and it grows quickly. It also seriously affects node startup time, most of what it's doing is reading these hashes, the longer the chain the more time it needs to do that. Notice that this doesn't change the underlying DB scheme in any way. |
||
|---|---|---|
| .. | ||
| compiler | ||
| config | ||
| consensus | ||
| core | ||
| crypto | ||
| encoding | ||
| interop | ||
| io | ||
| neorpc | ||
| neotest | ||
| network | ||
| rpcclient | ||
| services | ||
| smartcontract | ||
| util | ||
| vm | ||
| wallet | ||