Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate archive node performance #1870

Open
olehnikolaiev opened this issue Apr 16, 2024 · 3 comments · May be fixed by #2063
Open

Investigate archive node performance #1870

olehnikolaiev opened this issue Apr 16, 2024 · 3 comments · May be fixed by #2063
Assignees
Milestone

Comments

@olehnikolaiev
Copy link
Contributor

archive node may catchup blocks slower then they appear on the core nodes and may have a long response time for json-rpc calls. need to investigate the reasons

@OleksanderSalamatov
Copy link

Added grafana monitoring for Exorde sync node
https://skale-grafana.skaleserver.com/d/ExordeSync/exorde-sync-node-hardware-overview
For credentials DM @OleksanderSalamatov

@DmytroNazarenko DmytroNazarenko changed the title investigate archive node performance Investigate archive node performance Apr 17, 2024
@olehnikolaiev
Copy link
Contributor Author

moving from leveldb to rocks db can potentially improve performance. need to investigate

@olehnikolaiev olehnikolaiev moved this from Ready For Pickup to In Progress in SKALE Engineering 🚀 Jul 9, 2024
olehnikolaiev added a commit that referenced this issue Jul 25, 2024
olehnikolaiev added a commit that referenced this issue Jul 29, 2024
olehnikolaiev added a commit that referenced this issue Aug 1, 2024
olehnikolaiev added a commit that referenced this issue Sep 23, 2024
olehnikolaiev added a commit that referenced this issue Sep 23, 2024
olehnikolaiev added a commit that referenced this issue Sep 25, 2024
olehnikolaiev added a commit that referenced this issue Sep 30, 2024
@PolinaKiporenko PolinaKiporenko modified the milestones: SKALE 3.1, SKALE 3.1.1 Oct 2, 2024
@dimalit
Copy link
Contributor

dimalit commented Oct 4, 2024

Block creation steps:

  1. m_state = m_state.createNewCopyWithLocks();
  2. m_state.mutableHistoricState().rotateDbsIfNeeded( _timestamp );
  3. Block::m_state = m_state.createStateModifyCopyAndPassLock();
  4. State stateSnapshot = Block::m_state.createStateModifyCopyAndPassLock();
  5. Run EVM
  6. stateSnapshot.commit()
  7. Repeat steps 4-6 for each transaction
  8. Block::m_state.mutableHistoricState().saveRootForBlock( m_currentBlock.number() );
  9. Block::m_state.releaseWriteLock();
  10. m_state = m_state.createNewCopyWithLocks();
  11. m_state.mutableHistoricState().setRoot( m_working.mutableState().mutableHistoricState().globalRoot() );

olehnikolaiev added a commit that referenced this issue Oct 7, 2024
olehnikolaiev added a commit that referenced this issue Oct 7, 2024
olehnikolaiev added a commit that referenced this issue Oct 7, 2024
olehnikolaiev added a commit that referenced this issue Oct 7, 2024
olehnikolaiev added a commit that referenced this issue Oct 16, 2024
olehnikolaiev added a commit that referenced this issue Oct 29, 2024
olehnikolaiev added a commit that referenced this issue Nov 1, 2024
olehnikolaiev added a commit that referenced this issue Nov 1, 2024
olehnikolaiev added a commit that referenced this issue Nov 4, 2024
olehnikolaiev added a commit that referenced this issue Nov 4, 2024
olehnikolaiev added a commit that referenced this issue Nov 4, 2024
@olehnikolaiev olehnikolaiev linked a pull request Jan 2, 2025 that will close this issue
@olehnikolaiev olehnikolaiev moved this from In Progress to Code Review in SKALE Engineering 🚀 Jan 6, 2025
@olehnikolaiev olehnikolaiev linked a pull request Jan 13, 2025 that will close this issue
olehnikolaiev added a commit that referenced this issue Jan 13, 2025
olehnikolaiev added a commit that referenced this issue Jan 13, 2025
olehnikolaiev added a commit that referenced this issue Jan 13, 2025
@PolinaKiporenko PolinaKiporenko removed the bug Something isn't working label Jan 16, 2025
olehnikolaiev added a commit that referenced this issue Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Code Review
Development

Successfully merging a pull request may close this issue.

4 participants