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

Week 9 - November 23 - state history requires too much RAM #108

Open
Tracked by #37
chillsauce opened this issue Nov 23, 2022 · 1 comment
Open
Tracked by #37

Week 9 - November 23 - state history requires too much RAM #108

chillsauce opened this issue Nov 23, 2022 · 1 comment

Comments

@chillsauce
Copy link
Member

chillsauce commented Nov 23, 2022

The EOS Node Operator Roundtable (formerly, Antelope Leap upgrade working group) meets every Wednesday at 14:00 UTC to prepare for the next EOS consensus upgrade.

💬 Join us in Telegram
🗂 See all meeting summaries

🗓 November 23 - 14:00 UTC

🎥 Watch the recording

  • Passcode: 1Gx@h=9e

Summary

🟢 Leap Software Status

#41

  • Recent release:
  • Antelope software/documentation updates on the way:
    • Document on how crypto extensions inside CDT to utilize crypto primitive host functions
    • System contract updates
    • Release of DUNE in the next month

Technical roundtable for EOS Node Operators

  • This week, we hosted a technical discussion on state database trimming, proposed by Michael from EOSUSA.
    • Reframed - The problem: we use too much RAM for storing state history, and it keeps getting bigger and harder to manage.
    • Question posed:
      • What are the trade-offs we're willing to make in performance vs RAM size?
        • Answer: willing to trade-off 1 block production cycle for loading data into RAM (like a warming block)?
          • this comes with risk of abuse

Short term opportunities

  • An RFP is being drafted by the Antelope coalition to research this issue.
  • Make Heap mode startup and shutdown faster
  • is there an opportunity to make the tmpfs more out of the box?
  • Leaving account queries disabled can save on RAM (opportunity for node operator configuration, already possible)
  • Store account queries to disk (maybe 4GB for roughly 14M accounts on WAX of ram in savings here, probably not worth it)

Long term opportunities

  • Can smart contracts be incentivized to specify RAM vs Disk storage?
  • Hardware vendors need to start offering very fast CPU cores with high amounts of RAM

Next week

  • For next week, Matthew from EOS Nation has proposed a discussion on what statistics should be added to the prometheus exporter in Leap 4.0.
    • nodeEOS is a black box, we have no idea what's happening, let's provide some statistics
    • Bring your list of what you'd like to have in prometheus to the next call

Participants (14)

  • Max_Cho :: KOREOS Owner-South Korea
  • Randall Roland
  • Matt Witherspoon
  • Kevin Heifner
  • Brian Hazzard
  • Stephen Diesel
  • Daniel Keyes | EOS Nation
  • Corvin Meyer auf der Heide
  • Jannis - Rakeden (Jannis)
  • Matthew Darwin
  • Patrick - Aloha EOS (Patrick Burns)
  • Ross (EOSphere)
  • Corvin Meyer auf der Heide - cmadh | liquiid.io (Corvin Meyer auf der Heide)
  • Dario | EOSsupport.io
@marconamaste
Copy link

Ad long term opportunities: Hardware. There's workstations with 28 cores and up to 1.5 TB of RAM. https://www.apple.com/uk/mac-pro/specs/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants