Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Multi-thread transaction key recovery #6149

Merged
merged 15 commits into from
Oct 26, 2018
Merged

Multi-thread transaction key recovery #6149

merged 15 commits into from
Oct 26, 2018

Conversation

heifner
Copy link
Contributor

@heifner heifner commented Oct 25, 2018

Change Description

  • Transaction key recovery is now done on separate threads via a thread pool in the controller when applying a signed block.

Consensus Changes

None

API Changes

  • chain_plugin has new configuration option:
    -- chain-threads - number of threads for the controller thread_pool. Currently used for transaction key recovery, but could be used for other operations in the future.

Documentation Additions

  • New chain-threads nodeos configuration option chain-threads - number of threads to use for transaction key recovery when applying a signed block.

@wanderingbort wanderingbort merged commit 073344a into develop Oct 26, 2018
@wanderingbort wanderingbort deleted the key-perf branch October 26, 2018 06:29
@@ -25,6 +26,7 @@ struct block_header_state {
public_key_type block_signing_key;
vector<uint8_t> confirm_count;
vector<header_confirmation> confirmations;
std::shared_future<public_key_type> block_signing_key_future;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't seem to be used? was there some files left out of this PR (despite it operating fine)? Or is this future expansion

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was experimenting with block signing future. I'll remove this.

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

Successfully merging this pull request may close these issues.

2 participants