Skip to content
New issue

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

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

Already on GitHub? # to your account

DP: Answer the question: When enabling which SteemD plugins require a chain replay #2909

Open
1 task
relativityboy opened this issue Sep 17, 2018 · 1 comment
Labels
5 - SW Steemworks Points spike

Comments

@relativityboy
Copy link
Contributor

As a developer I want to know which combinations of SteemD plugins are inter-compatible in-terms of their shared memory files.

examples:

  1. Plugins a & b are run from when the node was first created. The node is stopped, and plugin c is enabled on restart. No problems. The node is stopped and plugin d is enabled. Problems.
  2. Plugin d is run from when the node was first created. The node is stopped, and plugin a is enabled on restart. Problems.
  3. Plugin c is run from when the node was first created. The node is stopped, and any of plugins a, b, or are enabled on restart. Problems.
  4. Plugins a & d are run from when the node was first created. The node is stopped, and plugins c & b are enabled on restart. No Problems.

Supporting Definitions (names can be changed)

  • Plugin Group - a set of plugins where if any one of them has been enabled since node 1st created, the other plugins in the group can be enabled at a later date.
  • Uncle Plugin - a plugin that creates a node memory situation where at least one other plugin can be added at a later time, that would not have been able to be added were Parent not enabled.
  • Nephew Plugin - depends on either being enabled since node creation, or on an Uncle Plugin being enabled since node creation.
  • Clean Plugin - Plugins that can be enabled at any time, regardless of what other plugins have/haven't been enabled.

AC

  • # Results listing all sets of plugins in their above definitions
@inertia186
Copy link

For example, I have an intel skull canyon nuc with 32 GB RAM, ubuntu 16.04. Doing a replay with the following plugins is super slow (greater than 24 hours on --replay-blockchain):

plugin = chain p2p webserver block_api database_api network_broadcast_api condenser_api market_history_api tags_api follow_api

However, if I drop the last three plugins, the reply is less than 8 hours:

plugin = chain p2p webserver block_api database_api network_broadcast_api condenser_api

Once the replay is complete, if I add market_history_api tags_api follow_api, startup slows down a little, but it doesn't require a replay.

@relativityboy relativityboy added 5 - SW Steemworks Points and removed 5 labels Sep 21, 2018
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
5 - SW Steemworks Points spike
Projects
None yet
Development

No branches or pull requests

2 participants