1. 13 Jul, 2023 5 commits
  2. 12 Jul, 2023 4 commits
  3. 11 Jul, 2023 7 commits
  4. 10 Jul, 2023 1 commit
  5. 07 Jul, 2023 1 commit
  6. 06 Jul, 2023 5 commits
  7. 05 Jul, 2023 1 commit
  8. 04 Jul, 2023 1 commit
    • rjl493456442's avatar
      cmd, core, eth, graphql, trie: no persisted clean trie cache file (#27525) · 59f7b289
      rjl493456442 authored
      The clean trie cache is persisted periodically, therefore Geth can
      quickly warmup the cache in next restart.
      
      However it will reduce the robustness of system. The assumption is
      held in Geth that if the parent trie node is present, then the entire
      sub-trie associated with the parent are all prensent.
      
      Imagine the scenario that Geth rewinds itself to a past block and
      restart, but Geth finds the root node of "future state" in clean
      cache then regard this state is present in disk, while is not in fact.
      
      Another example is offline pruning tool. Whenever an offline pruning
      is performed, the clean cache file has to be removed to aviod hitting
      the root node of "deleted states" in clean cache.
      
      All in all, compare with the minor performance gain, system robustness
      is something we care more.
      59f7b289
  9. 02 Jul, 2023 1 commit
  10. 28 Jun, 2023 3 commits
  11. 27 Jun, 2023 8 commits
  12. 25 Jun, 2023 1 commit
  13. 23 Jun, 2023 1 commit
  14. 22 Jun, 2023 1 commit