-
Notifications
You must be signed in to change notification settings - Fork 2.3k
multi: memoize pubkey+signature decoding to reduce GC bursts, add reject cache to stop zombie churn #706
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
Merged
Roasbeef
merged 16 commits into
lightningnetwork:master
from
Roasbeef:gc-fixes-reject-cache
Feb 7, 2018
Merged
multi: memoize pubkey+signature decoding to reduce GC bursts, add reject cache to stop zombie churn #706
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
0d7b8be
lnwire: add new Sig type to handle conversion to/from btcec.Signature
Roasbeef 4dd108c
lnwire: replace usage of btcec.Signature with the new lnwire.Sig type
Roasbeef aa2e91f
lnwire: replace instances of *btcec.PublicKey with [33]byte in ann me…
Roasbeef 9c483c3
lnwallet: update state machine to use new lnwire.Sig everywhere
Roasbeef 850abbb
htlcswitch: update tests to respect recent API changes
Roasbeef 5e9166e
channeldb: use raw pub keys and signatures directly in vertex/edge st…
Roasbeef cd9d2d7
discovery: update graph API usage to match recent API changes
Roasbeef cb48a58
autopilot: update API usage to account for recent channeldb changes
Roasbeef 6751cd8
routing: update package to account for recent channeldb API changes
Roasbeef 9f02144
zpay32: update parsing to use new lnwire.Sig API
Roasbeef 22951cb
lnd: account for new lnwire.Sig API and channeldb API changes
Roasbeef 1f3124f
routing: use [33]byte instead of *btcutil.Publickey for SendToSwitch
Roasbeef 6d05cb5
routing: extract zombie pruning to distinct method
Roasbeef b54b8dd
routing: reject any new announcements which were pruned as zombies
Roasbeef e578cea
channeldb: fix linter errors
Roasbeef bf05e47
discovery: add additional gossiper level reject cache
Roasbeef File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this changes the behavior of the previous statement. Before, the bitcoin keys are always assigned as vertex1 then vertex2, even if the node keys are flipped. Here the bitcoin keys will take on the same ordering as the node keys.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The bitcoin keys aren't of importance as we only look at the node keys. This is for generating random graphs during tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh i see!