Smart settle - #5113
Merged
Merged
Conversation
Guillembonet
requested review from
Snawoot,
Waldz,
mdomasevicius,
soffokl,
tadaskay and
tomasmik
as code owners
May 12, 2022 09:25
Guillembonet
force-pushed
the
smart-auto-settle
branch
from
May 16, 2022 07:43
8052453 to
08c0902
Compare
Codecov Report
@@ Coverage Diff @@
## master #5113 +/- ##
==========================================
- Coverage 39.11% 39.03% -0.09%
==========================================
Files 359 359
Lines 19155 19208 +53
==========================================
+ Hits 7493 7497 +4
- Misses 10927 10973 +46
- Partials 735 738 +3
Continue to review full report at Codecov.
|
tomasmik
approved these changes
May 16, 2022
tomasmik
left a comment
Contributor
There was a problem hiding this comment.
I would probably just remove the cache, but it's fine either way.
n10ty
approved these changes
May 16, 2022
Guillembonet
force-pushed
the
smart-auto-settle
branch
from
May 16, 2022 09:30
08c0902 to
511bc66
Compare
tomasmik
reviewed
May 16, 2022
Guillembonet
force-pushed
the
smart-auto-settle
branch
from
May 16, 2022 09:42
511bc66 to
2df76f7
Compare
tomasmik
reviewed
May 16, 2022
tomasmik
approved these changes
May 16, 2022
Guillembonet
force-pushed
the
smart-auto-settle
branch
from
May 16, 2022 10:34
2df76f7 to
684fe2b
Compare
tomasmik
approved these changes
May 16, 2022
Signed-off-by: Guillem Bonet <guillem@mysterium.network>
Guillembonet
force-pushed
the
smart-auto-settle
branch
from
May 16, 2022 10:59
684fe2b to
3ea092a
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes: #5067
Current problems:
/feeendpoint a lot. In the last 3 minutes there are 1400 calls yet coming only from 550 different nodes.Proposed solutions:
3 minutes30 seconds (by default) instead of calling every time. Keep in mind that the smart settlement check requires a call there on every hermes promise received (only if we have more unsettled than 5), so with both changes, we might still call transactor/feeendpoint quite a lot but I think it should be less. We can discuss whether we should increase this cache amount a bit more (more than 10 mins will for sure be bad).Signed-off-by: Guillem Bonet guillem@mysterium.network