Improve router logging and update documentation - #2436

Merged
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging
Jul 21, 2023
Merged

Improve router logging and update documentation#2436
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging

Conversation

@tnull

@tnulltnull commented Jul 21, 2023

Copy link
Copy Markdown
Contributor

Fixes#1646

As #2417 will slip to a future release, this PR just includes the improved logging and documentation fixups of of our router.

Previously, we barely gave any hints why we excluded certain hops during pathfinding. Here, we introduce more verbose logging by a) accounting how much candidates we ignored for which reasons and b) logging any first/last/blinded hops we end up ignoring.

We also improve documentation as RouteParameters are not included in Event::PaymentPathFailed since 0.0.115, and we don't give value/payee as immediate arguments to find_route anymore.

@tnull

Copy link
Copy Markdown
ContributorAuthor

Just to carry over some of the context here, the benches from #2417 with n = 10000 (on Linux on Intel(R) Xeon(R) CPU E3-1226 v3 @ 3.30GHz) interestingly indicate the logging changes actually maintain or even improve the pathfinding performance:

Benchmarking generate_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1208.3 s (10k iterations)
Benchmarking generate_routes_with_zero_penalty_scorer: Analyzing
generate_routes_with_zero_penalty_scorer
time: [118.83 ms 119.77 ms 120.71 ms]
change: [-1.7780% -0.4836% +0.7940%] (p = 0.45 > 0.05)
No change in performance detected.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1139.0 s (10k iterations)
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Analyzing
generate_mpp_routes_with_zero_penalty_scorer
time: [110.90 ms 111.74 ms 112.58 ms]
change: [-11.985% -10.971% -9.9144%] (p = 0.00 < 0.05)
Performance has improved.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1587.6 s (10k iterations)
Benchmarking generate_routes_with_probabilistic_scorer: Analyzing
generate_routes_with_probabilistic_scorer
time: [158.24 ms 158.62 ms 159.00 ms]
change: [-2.6897% -2.4127% -2.1132%] (p = 0.00 < 0.05)
Performance has improved.
Found 183 outliers among 10000 measurements (1.83%)
183 (1.83%) low mild
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1552.4 s (10k iterations)
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Analyzing
generate_mpp_routes_with_probabilistic_scorer
time: [156.10 ms 156.53 ms 156.96 ms]
change: [-1.8478% -1.4928% -1.1282%] (p = 0.00 < 0.05)
Performance has improved.
Found 200 outliers among 10000 measurements (2.00%)
200 (2.00%) high mild
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 3672.8 s (10k iterations)
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Analyzing
generate_large_mpp_routes_with_probabilistic_scorer
time: [349.39 ms 354.79 ms 360.26 ms]
change: [-15.815% -14.168% -12.477%] (p = 0.00 < 0.05)
Performance has improved.
Found 1400 outliers among 10000 measurements (14.00%)
802 (8.02%) high mild
598 (5.98%) high severe

@tnulltnull added this to the 0.0.116 milestone Jul 21, 2023
@codecov-commenter

codecov-commenter commented Jul 21, 2023

Copy link
Copy Markdown

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.71 🎉

Comparison is base (e4c44f3) 90.24% compared to head (14f5544) 90.96%.

❗ Current head 14f5544 differs from pull request most recent head 1db53a9. Consider uploading reports for the commit 1db53a9 to get more accurate results

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files
@@ Coverage Diff @@## main #2436 +/- ##
==========================================
+ Coverage 90.24% 90.96% +0.71% 
==========================================
Files 106 106 Lines 55774 62618 +6844 Branches 55774 62618 +6844 ==========================================
+ Hits 50335 56959 +6624 - Misses 5439 5659 +220 
Impacted FilesCoverage Δ
lightning/src/routing/router.rs93.51% <100.00%> (+0.16%)⬆️

... and 10 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Comment threadlightning/src/routing/router.rs Outdated
Comment threadlightning/src/routing/router.rs Outdated
Comment on lines -1721 to +1761
if !contributes_sufficient_value || exceeds_max_path_length ||
exceeds_cltv_delta_limit || payment_failed_on_this_channel {
// Path isn't useful, ignore it and move on.
if !contributes_sufficient_value {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to insufficient value contribution.", LoggedCandidateHop(&$candidate));
}
num_ignored_value_contribution += 1;
} else if exceeds_max_path_length {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding max. path length limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_path_length_limit += 1;
} else if exceeds_cltv_delta_limit {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding CLTV delta limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_cltv_delta_limit += 1;
} else if payment_failed_on_this_channel {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to a failed previous payment attempt.", LoggedCandidateHop(&$candidate));
}
num_ignored_previously_failed += 1;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

@valentinewallacevalentinewallaceJul 21, 2023

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

True, might be best to just have one long log that includes all the variables, which would remove all the branching as well

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

Not necessarily, but we log and count the first reason why a candidate would be excluded. Yes, some should count towards multiple categories, but it's probably not worth to check for all combinations.

True, might be best to just have one long log that includes all the variables

Mh, I think even if some candidates might fall under multiple categories, it's much more readable to have individual logs?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think its useful to have individual reasons why a particular candidate was ignored.

@jkczyzjkczyz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM. Please squash

tnull added 2 commits July 21, 2023 20:28
As `RouteParameters` are not included anymore in
`Event::PaymentPathFailed` since 0.0.115, and we don't give value/payee
as immediate arguments to `find_route` anymore.
Previously, we barely gave any hints why we excluded certain hops during
pathfinding. Here, we introduce more verbose logging by a) accounting
how much candidates we ignored for which reasons and b) logging any
first/last/blinded hops we end up ignoring.
Fixeslightningdevkit#1646.
@tnull
tnullforce-pushed the 2023-07-improve-router-logging branch from fd94350 to 1db53a9CompareJuly 21, 2023 18:28
@tnull

Copy link
Copy Markdown
ContributorAuthor

LGTM. Please squash

Squashed without further changes.

@jkczyz
jkczyz merged commit 0fadb54 into lightningdevkit:mainJul 21, 2023
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve logging of pathfinding behavior

6 participants

@tnull@codecov-commenter@TheBlueMatt@G8XSU@jkczyz@valentinewallace
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

Improve router logging and update documentation - #2436

Merged
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging
Jul 21, 2023
Merged

Improve router logging and update documentation#2436
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging

Conversation

@tnull

@tnulltnull commented Jul 21, 2023

Copy link
Copy Markdown
Contributor

Fixes#1646

As #2417 will slip to a future release, this PR just includes the improved logging and documentation fixups of of our router.

Previously, we barely gave any hints why we excluded certain hops during pathfinding. Here, we introduce more verbose logging by a) accounting how much candidates we ignored for which reasons and b) logging any first/last/blinded hops we end up ignoring.

We also improve documentation as RouteParameters are not included in Event::PaymentPathFailed since 0.0.115, and we don't give value/payee as immediate arguments to find_route anymore.

@tnull

Copy link
Copy Markdown
ContributorAuthor

Just to carry over some of the context here, the benches from #2417 with n = 10000 (on Linux on Intel(R) Xeon(R) CPU E3-1226 v3 @ 3.30GHz) interestingly indicate the logging changes actually maintain or even improve the pathfinding performance:

Benchmarking generate_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1208.3 s (10k iterations)
Benchmarking generate_routes_with_zero_penalty_scorer: Analyzing
generate_routes_with_zero_penalty_scorer
time: [118.83 ms 119.77 ms 120.71 ms]
change: [-1.7780% -0.4836% +0.7940%] (p = 0.45 > 0.05)
No change in performance detected.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1139.0 s (10k iterations)
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Analyzing
generate_mpp_routes_with_zero_penalty_scorer
time: [110.90 ms 111.74 ms 112.58 ms]
change: [-11.985% -10.971% -9.9144%] (p = 0.00 < 0.05)
Performance has improved.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1587.6 s (10k iterations)
Benchmarking generate_routes_with_probabilistic_scorer: Analyzing
generate_routes_with_probabilistic_scorer
time: [158.24 ms 158.62 ms 159.00 ms]
change: [-2.6897% -2.4127% -2.1132%] (p = 0.00 < 0.05)
Performance has improved.
Found 183 outliers among 10000 measurements (1.83%)
183 (1.83%) low mild
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1552.4 s (10k iterations)
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Analyzing
generate_mpp_routes_with_probabilistic_scorer
time: [156.10 ms 156.53 ms 156.96 ms]
change: [-1.8478% -1.4928% -1.1282%] (p = 0.00 < 0.05)
Performance has improved.
Found 200 outliers among 10000 measurements (2.00%)
200 (2.00%) high mild
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 3672.8 s (10k iterations)
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Analyzing
generate_large_mpp_routes_with_probabilistic_scorer
time: [349.39 ms 354.79 ms 360.26 ms]
change: [-15.815% -14.168% -12.477%] (p = 0.00 < 0.05)
Performance has improved.
Found 1400 outliers among 10000 measurements (14.00%)
802 (8.02%) high mild
598 (5.98%) high severe

@tnulltnull added this to the 0.0.116 milestone Jul 21, 2023
@codecov-commenter

codecov-commenter commented Jul 21, 2023

Copy link
Copy Markdown

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.71 🎉

Comparison is base (e4c44f3) 90.24% compared to head (14f5544) 90.96%.

❗ Current head 14f5544 differs from pull request most recent head 1db53a9. Consider uploading reports for the commit 1db53a9 to get more accurate results

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files
@@ Coverage Diff @@## main #2436 +/- ##
==========================================
+ Coverage 90.24% 90.96% +0.71% 
==========================================
Files 106 106 Lines 55774 62618 +6844 Branches 55774 62618 +6844 ==========================================
+ Hits 50335 56959 +6624 - Misses 5439 5659 +220 
Impacted FilesCoverage Δ
lightning/src/routing/router.rs93.51% <100.00%> (+0.16%)⬆️

... and 10 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Comment threadlightning/src/routing/router.rs Outdated
Comment threadlightning/src/routing/router.rs Outdated
Comment on lines -1721 to +1761
if !contributes_sufficient_value || exceeds_max_path_length ||
exceeds_cltv_delta_limit || payment_failed_on_this_channel {
// Path isn't useful, ignore it and move on.
if !contributes_sufficient_value {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to insufficient value contribution.", LoggedCandidateHop(&$candidate));
}
num_ignored_value_contribution += 1;
} else if exceeds_max_path_length {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding max. path length limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_path_length_limit += 1;
} else if exceeds_cltv_delta_limit {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding CLTV delta limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_cltv_delta_limit += 1;
} else if payment_failed_on_this_channel {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to a failed previous payment attempt.", LoggedCandidateHop(&$candidate));
}
num_ignored_previously_failed += 1;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

@valentinewallacevalentinewallaceJul 21, 2023

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

True, might be best to just have one long log that includes all the variables, which would remove all the branching as well

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

Not necessarily, but we log and count the first reason why a candidate would be excluded. Yes, some should count towards multiple categories, but it's probably not worth to check for all combinations.

True, might be best to just have one long log that includes all the variables

Mh, I think even if some candidates might fall under multiple categories, it's much more readable to have individual logs?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think its useful to have individual reasons why a particular candidate was ignored.

@jkczyzjkczyz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM. Please squash

tnull added 2 commits July 21, 2023 20:28
As `RouteParameters` are not included anymore in
`Event::PaymentPathFailed` since 0.0.115, and we don't give value/payee
as immediate arguments to `find_route` anymore.
Previously, we barely gave any hints why we excluded certain hops during
pathfinding. Here, we introduce more verbose logging by a) accounting
how much candidates we ignored for which reasons and b) logging any
first/last/blinded hops we end up ignoring.
Fixeslightningdevkit#1646.
@tnull
tnullforce-pushed the 2023-07-improve-router-logging branch from fd94350 to 1db53a9CompareJuly 21, 2023 18:28
@tnull

Copy link
Copy Markdown
ContributorAuthor

LGTM. Please squash

Squashed without further changes.

@jkczyz
jkczyz merged commit 0fadb54 into lightningdevkit:mainJul 21, 2023
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve logging of pathfinding behavior

6 participants

@tnull@codecov-commenter@TheBlueMatt@G8XSU@jkczyz@valentinewallace
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Improve router logging and update documentation - #2436

Merged
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging
Jul 21, 2023
Merged

Improve router logging and update documentation#2436
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging

Conversation

@tnull

@tnulltnull commented Jul 21, 2023

Copy link
Copy Markdown
Contributor

Fixes#1646

As #2417 will slip to a future release, this PR just includes the improved logging and documentation fixups of of our router.

Previously, we barely gave any hints why we excluded certain hops during pathfinding. Here, we introduce more verbose logging by a) accounting how much candidates we ignored for which reasons and b) logging any first/last/blinded hops we end up ignoring.

We also improve documentation as RouteParameters are not included in Event::PaymentPathFailed since 0.0.115, and we don't give value/payee as immediate arguments to find_route anymore.

@tnull

Copy link
Copy Markdown
ContributorAuthor

Just to carry over some of the context here, the benches from #2417 with n = 10000 (on Linux on Intel(R) Xeon(R) CPU E3-1226 v3 @ 3.30GHz) interestingly indicate the logging changes actually maintain or even improve the pathfinding performance:

Benchmarking generate_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1208.3 s (10k iterations)
Benchmarking generate_routes_with_zero_penalty_scorer: Analyzing
generate_routes_with_zero_penalty_scorer
time: [118.83 ms 119.77 ms 120.71 ms]
change: [-1.7780% -0.4836% +0.7940%] (p = 0.45 > 0.05)
No change in performance detected.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1139.0 s (10k iterations)
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Analyzing
generate_mpp_routes_with_zero_penalty_scorer
time: [110.90 ms 111.74 ms 112.58 ms]
change: [-11.985% -10.971% -9.9144%] (p = 0.00 < 0.05)
Performance has improved.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1587.6 s (10k iterations)
Benchmarking generate_routes_with_probabilistic_scorer: Analyzing
generate_routes_with_probabilistic_scorer
time: [158.24 ms 158.62 ms 159.00 ms]
change: [-2.6897% -2.4127% -2.1132%] (p = 0.00 < 0.05)
Performance has improved.
Found 183 outliers among 10000 measurements (1.83%)
183 (1.83%) low mild
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1552.4 s (10k iterations)
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Analyzing
generate_mpp_routes_with_probabilistic_scorer
time: [156.10 ms 156.53 ms 156.96 ms]
change: [-1.8478% -1.4928% -1.1282%] (p = 0.00 < 0.05)
Performance has improved.
Found 200 outliers among 10000 measurements (2.00%)
200 (2.00%) high mild
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 3672.8 s (10k iterations)
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Analyzing
generate_large_mpp_routes_with_probabilistic_scorer
time: [349.39 ms 354.79 ms 360.26 ms]
change: [-15.815% -14.168% -12.477%] (p = 0.00 < 0.05)
Performance has improved.
Found 1400 outliers among 10000 measurements (14.00%)
802 (8.02%) high mild
598 (5.98%) high severe

@tnulltnull added this to the 0.0.116 milestone Jul 21, 2023
@codecov-commenter

codecov-commenter commented Jul 21, 2023

Copy link
Copy Markdown

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.71 🎉

Comparison is base (e4c44f3) 90.24% compared to head (14f5544) 90.96%.

❗ Current head 14f5544 differs from pull request most recent head 1db53a9. Consider uploading reports for the commit 1db53a9 to get more accurate results

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files
@@ Coverage Diff @@## main #2436 +/- ##
==========================================
+ Coverage 90.24% 90.96% +0.71% 
==========================================
Files 106 106 Lines 55774 62618 +6844 Branches 55774 62618 +6844 ==========================================
+ Hits 50335 56959 +6624 - Misses 5439 5659 +220 
Impacted FilesCoverage Δ
lightning/src/routing/router.rs93.51% <100.00%> (+0.16%)⬆️

... and 10 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Comment threadlightning/src/routing/router.rs Outdated
Comment threadlightning/src/routing/router.rs Outdated
Comment on lines -1721 to +1761
if !contributes_sufficient_value || exceeds_max_path_length ||
exceeds_cltv_delta_limit || payment_failed_on_this_channel {
// Path isn't useful, ignore it and move on.
if !contributes_sufficient_value {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to insufficient value contribution.", LoggedCandidateHop(&$candidate));
}
num_ignored_value_contribution += 1;
} else if exceeds_max_path_length {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding max. path length limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_path_length_limit += 1;
} else if exceeds_cltv_delta_limit {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding CLTV delta limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_cltv_delta_limit += 1;
} else if payment_failed_on_this_channel {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to a failed previous payment attempt.", LoggedCandidateHop(&$candidate));
}
num_ignored_previously_failed += 1;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

@valentinewallacevalentinewallaceJul 21, 2023

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

True, might be best to just have one long log that includes all the variables, which would remove all the branching as well

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

Not necessarily, but we log and count the first reason why a candidate would be excluded. Yes, some should count towards multiple categories, but it's probably not worth to check for all combinations.

True, might be best to just have one long log that includes all the variables

Mh, I think even if some candidates might fall under multiple categories, it's much more readable to have individual logs?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think its useful to have individual reasons why a particular candidate was ignored.

@jkczyzjkczyz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM. Please squash

tnull added 2 commits July 21, 2023 20:28
As `RouteParameters` are not included anymore in
`Event::PaymentPathFailed` since 0.0.115, and we don't give value/payee
as immediate arguments to `find_route` anymore.
Previously, we barely gave any hints why we excluded certain hops during
pathfinding. Here, we introduce more verbose logging by a) accounting
how much candidates we ignored for which reasons and b) logging any
first/last/blinded hops we end up ignoring.
Fixeslightningdevkit#1646.
@tnull
tnullforce-pushed the 2023-07-improve-router-logging branch from fd94350 to 1db53a9CompareJuly 21, 2023 18:28
@tnull

Copy link
Copy Markdown
ContributorAuthor

LGTM. Please squash

Squashed without further changes.

@jkczyz
jkczyz merged commit 0fadb54 into lightningdevkit:mainJul 21, 2023
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve logging of pathfinding behavior

6 participants

@tnull@codecov-commenter@TheBlueMatt@G8XSU@jkczyz@valentinewallace
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Improve router logging and update documentation - #2436

Merged
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging
Jul 21, 2023
Merged

Improve router logging and update documentation#2436
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging

Conversation

@tnull

@tnulltnull commented Jul 21, 2023

Copy link
Copy Markdown
Contributor

Fixes#1646

As #2417 will slip to a future release, this PR just includes the improved logging and documentation fixups of of our router.

Previously, we barely gave any hints why we excluded certain hops during pathfinding. Here, we introduce more verbose logging by a) accounting how much candidates we ignored for which reasons and b) logging any first/last/blinded hops we end up ignoring.

We also improve documentation as RouteParameters are not included in Event::PaymentPathFailed since 0.0.115, and we don't give value/payee as immediate arguments to find_route anymore.

@tnull

Copy link
Copy Markdown
ContributorAuthor

Just to carry over some of the context here, the benches from #2417 with n = 10000 (on Linux on Intel(R) Xeon(R) CPU E3-1226 v3 @ 3.30GHz) interestingly indicate the logging changes actually maintain or even improve the pathfinding performance:

Benchmarking generate_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1208.3 s (10k iterations)
Benchmarking generate_routes_with_zero_penalty_scorer: Analyzing
generate_routes_with_zero_penalty_scorer
time: [118.83 ms 119.77 ms 120.71 ms]
change: [-1.7780% -0.4836% +0.7940%] (p = 0.45 > 0.05)
No change in performance detected.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1139.0 s (10k iterations)
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Analyzing
generate_mpp_routes_with_zero_penalty_scorer
time: [110.90 ms 111.74 ms 112.58 ms]
change: [-11.985% -10.971% -9.9144%] (p = 0.00 < 0.05)
Performance has improved.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1587.6 s (10k iterations)
Benchmarking generate_routes_with_probabilistic_scorer: Analyzing
generate_routes_with_probabilistic_scorer
time: [158.24 ms 158.62 ms 159.00 ms]
change: [-2.6897% -2.4127% -2.1132%] (p = 0.00 < 0.05)
Performance has improved.
Found 183 outliers among 10000 measurements (1.83%)
183 (1.83%) low mild
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1552.4 s (10k iterations)
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Analyzing
generate_mpp_routes_with_probabilistic_scorer
time: [156.10 ms 156.53 ms 156.96 ms]
change: [-1.8478% -1.4928% -1.1282%] (p = 0.00 < 0.05)
Performance has improved.
Found 200 outliers among 10000 measurements (2.00%)
200 (2.00%) high mild
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 3672.8 s (10k iterations)
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Analyzing
generate_large_mpp_routes_with_probabilistic_scorer
time: [349.39 ms 354.79 ms 360.26 ms]
change: [-15.815% -14.168% -12.477%] (p = 0.00 < 0.05)
Performance has improved.
Found 1400 outliers among 10000 measurements (14.00%)
802 (8.02%) high mild
598 (5.98%) high severe

@tnulltnull added this to the 0.0.116 milestone Jul 21, 2023
@codecov-commenter

codecov-commenter commented Jul 21, 2023

Copy link
Copy Markdown

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.71 🎉

Comparison is base (e4c44f3) 90.24% compared to head (14f5544) 90.96%.

❗ Current head 14f5544 differs from pull request most recent head 1db53a9. Consider uploading reports for the commit 1db53a9 to get more accurate results

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files
@@ Coverage Diff @@## main #2436 +/- ##
==========================================
+ Coverage 90.24% 90.96% +0.71% 
==========================================
Files 106 106 Lines 55774 62618 +6844 Branches 55774 62618 +6844 ==========================================
+ Hits 50335 56959 +6624 - Misses 5439 5659 +220 
Impacted FilesCoverage Δ
lightning/src/routing/router.rs93.51% <100.00%> (+0.16%)⬆️

... and 10 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Comment threadlightning/src/routing/router.rs Outdated
Comment threadlightning/src/routing/router.rs Outdated
Comment on lines -1721 to +1761
if !contributes_sufficient_value || exceeds_max_path_length ||
exceeds_cltv_delta_limit || payment_failed_on_this_channel {
// Path isn't useful, ignore it and move on.
if !contributes_sufficient_value {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to insufficient value contribution.", LoggedCandidateHop(&$candidate));
}
num_ignored_value_contribution += 1;
} else if exceeds_max_path_length {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding max. path length limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_path_length_limit += 1;
} else if exceeds_cltv_delta_limit {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding CLTV delta limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_cltv_delta_limit += 1;
} else if payment_failed_on_this_channel {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to a failed previous payment attempt.", LoggedCandidateHop(&$candidate));
}
num_ignored_previously_failed += 1;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

@valentinewallacevalentinewallaceJul 21, 2023

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

True, might be best to just have one long log that includes all the variables, which would remove all the branching as well

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

Not necessarily, but we log and count the first reason why a candidate would be excluded. Yes, some should count towards multiple categories, but it's probably not worth to check for all combinations.

True, might be best to just have one long log that includes all the variables

Mh, I think even if some candidates might fall under multiple categories, it's much more readable to have individual logs?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think its useful to have individual reasons why a particular candidate was ignored.

@jkczyzjkczyz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM. Please squash

tnull added 2 commits July 21, 2023 20:28
As `RouteParameters` are not included anymore in
`Event::PaymentPathFailed` since 0.0.115, and we don't give value/payee
as immediate arguments to `find_route` anymore.
Previously, we barely gave any hints why we excluded certain hops during
pathfinding. Here, we introduce more verbose logging by a) accounting
how much candidates we ignored for which reasons and b) logging any
first/last/blinded hops we end up ignoring.
Fixeslightningdevkit#1646.
@tnull
tnullforce-pushed the 2023-07-improve-router-logging branch from fd94350 to 1db53a9CompareJuly 21, 2023 18:28
@tnull

Copy link
Copy Markdown
ContributorAuthor

LGTM. Please squash

Squashed without further changes.

@jkczyz
jkczyz merged commit 0fadb54 into lightningdevkit:mainJul 21, 2023
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve logging of pathfinding behavior

6 participants

@tnull@codecov-commenter@TheBlueMatt@G8XSU@jkczyz@valentinewallace
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

Improve router logging and update documentation - #2436

Merged
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging
Jul 21, 2023
Merged

Improve router logging and update documentation#2436
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging

Conversation

@tnull

@tnulltnull commented Jul 21, 2023

Copy link
Copy Markdown
Contributor

Fixes#1646

As #2417 will slip to a future release, this PR just includes the improved logging and documentation fixups of of our router.

Previously, we barely gave any hints why we excluded certain hops during pathfinding. Here, we introduce more verbose logging by a) accounting how much candidates we ignored for which reasons and b) logging any first/last/blinded hops we end up ignoring.

We also improve documentation as RouteParameters are not included in Event::PaymentPathFailed since 0.0.115, and we don't give value/payee as immediate arguments to find_route anymore.

@tnull

Copy link
Copy Markdown
ContributorAuthor

Just to carry over some of the context here, the benches from #2417 with n = 10000 (on Linux on Intel(R) Xeon(R) CPU E3-1226 v3 @ 3.30GHz) interestingly indicate the logging changes actually maintain or even improve the pathfinding performance:

Benchmarking generate_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1208.3 s (10k iterations)
Benchmarking generate_routes_with_zero_penalty_scorer: Analyzing
generate_routes_with_zero_penalty_scorer
time: [118.83 ms 119.77 ms 120.71 ms]
change: [-1.7780% -0.4836% +0.7940%] (p = 0.45 > 0.05)
No change in performance detected.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1139.0 s (10k iterations)
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Analyzing
generate_mpp_routes_with_zero_penalty_scorer
time: [110.90 ms 111.74 ms 112.58 ms]
change: [-11.985% -10.971% -9.9144%] (p = 0.00 < 0.05)
Performance has improved.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1587.6 s (10k iterations)
Benchmarking generate_routes_with_probabilistic_scorer: Analyzing
generate_routes_with_probabilistic_scorer
time: [158.24 ms 158.62 ms 159.00 ms]
change: [-2.6897% -2.4127% -2.1132%] (p = 0.00 < 0.05)
Performance has improved.
Found 183 outliers among 10000 measurements (1.83%)
183 (1.83%) low mild
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1552.4 s (10k iterations)
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Analyzing
generate_mpp_routes_with_probabilistic_scorer
time: [156.10 ms 156.53 ms 156.96 ms]
change: [-1.8478% -1.4928% -1.1282%] (p = 0.00 < 0.05)
Performance has improved.
Found 200 outliers among 10000 measurements (2.00%)
200 (2.00%) high mild
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 3672.8 s (10k iterations)
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Analyzing
generate_large_mpp_routes_with_probabilistic_scorer
time: [349.39 ms 354.79 ms 360.26 ms]
change: [-15.815% -14.168% -12.477%] (p = 0.00 < 0.05)
Performance has improved.
Found 1400 outliers among 10000 measurements (14.00%)
802 (8.02%) high mild
598 (5.98%) high severe

@tnulltnull added this to the 0.0.116 milestone Jul 21, 2023
@codecov-commenter

codecov-commenter commented Jul 21, 2023

Copy link
Copy Markdown

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.71 🎉

Comparison is base (e4c44f3) 90.24% compared to head (14f5544) 90.96%.

❗ Current head 14f5544 differs from pull request most recent head 1db53a9. Consider uploading reports for the commit 1db53a9 to get more accurate results

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files
@@ Coverage Diff @@## main #2436 +/- ##
==========================================
+ Coverage 90.24% 90.96% +0.71% 
==========================================
Files 106 106 Lines 55774 62618 +6844 Branches 55774 62618 +6844 ==========================================
+ Hits 50335 56959 +6624 - Misses 5439 5659 +220 
Impacted FilesCoverage Δ
lightning/src/routing/router.rs93.51% <100.00%> (+0.16%)⬆️

... and 10 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Comment threadlightning/src/routing/router.rs Outdated
Comment threadlightning/src/routing/router.rs Outdated
Comment on lines -1721 to +1761
if !contributes_sufficient_value || exceeds_max_path_length ||
exceeds_cltv_delta_limit || payment_failed_on_this_channel {
// Path isn't useful, ignore it and move on.
if !contributes_sufficient_value {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to insufficient value contribution.", LoggedCandidateHop(&$candidate));
}
num_ignored_value_contribution += 1;
} else if exceeds_max_path_length {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding max. path length limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_path_length_limit += 1;
} else if exceeds_cltv_delta_limit {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding CLTV delta limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_cltv_delta_limit += 1;
} else if payment_failed_on_this_channel {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to a failed previous payment attempt.", LoggedCandidateHop(&$candidate));
}
num_ignored_previously_failed += 1;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

@valentinewallacevalentinewallaceJul 21, 2023

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

True, might be best to just have one long log that includes all the variables, which would remove all the branching as well

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

Not necessarily, but we log and count the first reason why a candidate would be excluded. Yes, some should count towards multiple categories, but it's probably not worth to check for all combinations.

True, might be best to just have one long log that includes all the variables

Mh, I think even if some candidates might fall under multiple categories, it's much more readable to have individual logs?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think its useful to have individual reasons why a particular candidate was ignored.

@jkczyzjkczyz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM. Please squash

tnull added 2 commits July 21, 2023 20:28
As `RouteParameters` are not included anymore in
`Event::PaymentPathFailed` since 0.0.115, and we don't give value/payee
as immediate arguments to `find_route` anymore.
Previously, we barely gave any hints why we excluded certain hops during
pathfinding. Here, we introduce more verbose logging by a) accounting
how much candidates we ignored for which reasons and b) logging any
first/last/blinded hops we end up ignoring.
Fixeslightningdevkit#1646.
@tnull
tnullforce-pushed the 2023-07-improve-router-logging branch from fd94350 to 1db53a9CompareJuly 21, 2023 18:28
@tnull

Copy link
Copy Markdown
ContributorAuthor

LGTM. Please squash

Squashed without further changes.

@jkczyz
jkczyz merged commit 0fadb54 into lightningdevkit:mainJul 21, 2023
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve logging of pathfinding behavior

6 participants

@tnull@codecov-commenter@TheBlueMatt@G8XSU@jkczyz@valentinewallace
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Improve router logging and update documentation - #2436

Merged
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging
Jul 21, 2023
Merged

Improve router logging and update documentation#2436
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging

Conversation

@tnull

@tnulltnull commented Jul 21, 2023

Copy link
Copy Markdown
Contributor

Fixes#1646

As #2417 will slip to a future release, this PR just includes the improved logging and documentation fixups of of our router.

Previously, we barely gave any hints why we excluded certain hops during pathfinding. Here, we introduce more verbose logging by a) accounting how much candidates we ignored for which reasons and b) logging any first/last/blinded hops we end up ignoring.

We also improve documentation as RouteParameters are not included in Event::PaymentPathFailed since 0.0.115, and we don't give value/payee as immediate arguments to find_route anymore.

@tnull

Copy link
Copy Markdown
ContributorAuthor

Just to carry over some of the context here, the benches from #2417 with n = 10000 (on Linux on Intel(R) Xeon(R) CPU E3-1226 v3 @ 3.30GHz) interestingly indicate the logging changes actually maintain or even improve the pathfinding performance:

Benchmarking generate_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1208.3 s (10k iterations)
Benchmarking generate_routes_with_zero_penalty_scorer: Analyzing
generate_routes_with_zero_penalty_scorer
time: [118.83 ms 119.77 ms 120.71 ms]
change: [-1.7780% -0.4836% +0.7940%] (p = 0.45 > 0.05)
No change in performance detected.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1139.0 s (10k iterations)
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Analyzing
generate_mpp_routes_with_zero_penalty_scorer
time: [110.90 ms 111.74 ms 112.58 ms]
change: [-11.985% -10.971% -9.9144%] (p = 0.00 < 0.05)
Performance has improved.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1587.6 s (10k iterations)
Benchmarking generate_routes_with_probabilistic_scorer: Analyzing
generate_routes_with_probabilistic_scorer
time: [158.24 ms 158.62 ms 159.00 ms]
change: [-2.6897% -2.4127% -2.1132%] (p = 0.00 < 0.05)
Performance has improved.
Found 183 outliers among 10000 measurements (1.83%)
183 (1.83%) low mild
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1552.4 s (10k iterations)
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Analyzing
generate_mpp_routes_with_probabilistic_scorer
time: [156.10 ms 156.53 ms 156.96 ms]
change: [-1.8478% -1.4928% -1.1282%] (p = 0.00 < 0.05)
Performance has improved.
Found 200 outliers among 10000 measurements (2.00%)
200 (2.00%) high mild
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 3672.8 s (10k iterations)
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Analyzing
generate_large_mpp_routes_with_probabilistic_scorer
time: [349.39 ms 354.79 ms 360.26 ms]
change: [-15.815% -14.168% -12.477%] (p = 0.00 < 0.05)
Performance has improved.
Found 1400 outliers among 10000 measurements (14.00%)
802 (8.02%) high mild
598 (5.98%) high severe

@tnulltnull added this to the 0.0.116 milestone Jul 21, 2023
@codecov-commenter

codecov-commenter commented Jul 21, 2023

Copy link
Copy Markdown

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.71 🎉

Comparison is base (e4c44f3) 90.24% compared to head (14f5544) 90.96%.

❗ Current head 14f5544 differs from pull request most recent head 1db53a9. Consider uploading reports for the commit 1db53a9 to get more accurate results

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files
@@ Coverage Diff @@## main #2436 +/- ##
==========================================
+ Coverage 90.24% 90.96% +0.71% 
==========================================
Files 106 106 Lines 55774 62618 +6844 Branches 55774 62618 +6844 ==========================================
+ Hits 50335 56959 +6624 - Misses 5439 5659 +220 
Impacted FilesCoverage Δ
lightning/src/routing/router.rs93.51% <100.00%> (+0.16%)⬆️

... and 10 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Comment threadlightning/src/routing/router.rs Outdated
Comment threadlightning/src/routing/router.rs Outdated
Comment on lines -1721 to +1761
if !contributes_sufficient_value || exceeds_max_path_length ||
exceeds_cltv_delta_limit || payment_failed_on_this_channel {
// Path isn't useful, ignore it and move on.
if !contributes_sufficient_value {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to insufficient value contribution.", LoggedCandidateHop(&$candidate));
}
num_ignored_value_contribution += 1;
} else if exceeds_max_path_length {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding max. path length limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_path_length_limit += 1;
} else if exceeds_cltv_delta_limit {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding CLTV delta limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_cltv_delta_limit += 1;
} else if payment_failed_on_this_channel {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to a failed previous payment attempt.", LoggedCandidateHop(&$candidate));
}
num_ignored_previously_failed += 1;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

@valentinewallacevalentinewallaceJul 21, 2023

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

True, might be best to just have one long log that includes all the variables, which would remove all the branching as well

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

Not necessarily, but we log and count the first reason why a candidate would be excluded. Yes, some should count towards multiple categories, but it's probably not worth to check for all combinations.

True, might be best to just have one long log that includes all the variables

Mh, I think even if some candidates might fall under multiple categories, it's much more readable to have individual logs?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think its useful to have individual reasons why a particular candidate was ignored.

@jkczyzjkczyz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM. Please squash

tnull added 2 commits July 21, 2023 20:28
As `RouteParameters` are not included anymore in
`Event::PaymentPathFailed` since 0.0.115, and we don't give value/payee
as immediate arguments to `find_route` anymore.
Previously, we barely gave any hints why we excluded certain hops during
pathfinding. Here, we introduce more verbose logging by a) accounting
how much candidates we ignored for which reasons and b) logging any
first/last/blinded hops we end up ignoring.
Fixeslightningdevkit#1646.
@tnull
tnullforce-pushed the 2023-07-improve-router-logging branch from fd94350 to 1db53a9CompareJuly 21, 2023 18:28
@tnull

Copy link
Copy Markdown
ContributorAuthor

LGTM. Please squash

Squashed without further changes.

@jkczyz
jkczyz merged commit 0fadb54 into lightningdevkit:mainJul 21, 2023
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve logging of pathfinding behavior

6 participants

@tnull@codecov-commenter@TheBlueMatt@G8XSU@jkczyz@valentinewallace
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Improve router logging and update documentation - #2436

Merged
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging
Jul 21, 2023
Merged

Improve router logging and update documentation#2436
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging

Conversation

@tnull

@tnulltnull commented Jul 21, 2023

Copy link
Copy Markdown
Contributor

Fixes#1646

As #2417 will slip to a future release, this PR just includes the improved logging and documentation fixups of of our router.

Previously, we barely gave any hints why we excluded certain hops during pathfinding. Here, we introduce more verbose logging by a) accounting how much candidates we ignored for which reasons and b) logging any first/last/blinded hops we end up ignoring.

We also improve documentation as RouteParameters are not included in Event::PaymentPathFailed since 0.0.115, and we don't give value/payee as immediate arguments to find_route anymore.

@tnull

Copy link
Copy Markdown
ContributorAuthor

Just to carry over some of the context here, the benches from #2417 with n = 10000 (on Linux on Intel(R) Xeon(R) CPU E3-1226 v3 @ 3.30GHz) interestingly indicate the logging changes actually maintain or even improve the pathfinding performance:

Benchmarking generate_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1208.3 s (10k iterations)
Benchmarking generate_routes_with_zero_penalty_scorer: Analyzing
generate_routes_with_zero_penalty_scorer
time: [118.83 ms 119.77 ms 120.71 ms]
change: [-1.7780% -0.4836% +0.7940%] (p = 0.45 > 0.05)
No change in performance detected.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1139.0 s (10k iterations)
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Analyzing
generate_mpp_routes_with_zero_penalty_scorer
time: [110.90 ms 111.74 ms 112.58 ms]
change: [-11.985% -10.971% -9.9144%] (p = 0.00 < 0.05)
Performance has improved.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1587.6 s (10k iterations)
Benchmarking generate_routes_with_probabilistic_scorer: Analyzing
generate_routes_with_probabilistic_scorer
time: [158.24 ms 158.62 ms 159.00 ms]
change: [-2.6897% -2.4127% -2.1132%] (p = 0.00 < 0.05)
Performance has improved.
Found 183 outliers among 10000 measurements (1.83%)
183 (1.83%) low mild
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1552.4 s (10k iterations)
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Analyzing
generate_mpp_routes_with_probabilistic_scorer
time: [156.10 ms 156.53 ms 156.96 ms]
change: [-1.8478% -1.4928% -1.1282%] (p = 0.00 < 0.05)
Performance has improved.
Found 200 outliers among 10000 measurements (2.00%)
200 (2.00%) high mild
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 3672.8 s (10k iterations)
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Analyzing
generate_large_mpp_routes_with_probabilistic_scorer
time: [349.39 ms 354.79 ms 360.26 ms]
change: [-15.815% -14.168% -12.477%] (p = 0.00 < 0.05)
Performance has improved.
Found 1400 outliers among 10000 measurements (14.00%)
802 (8.02%) high mild
598 (5.98%) high severe

@tnulltnull added this to the 0.0.116 milestone Jul 21, 2023
@codecov-commenter

codecov-commenter commented Jul 21, 2023

Copy link
Copy Markdown

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.71 🎉

Comparison is base (e4c44f3) 90.24% compared to head (14f5544) 90.96%.

❗ Current head 14f5544 differs from pull request most recent head 1db53a9. Consider uploading reports for the commit 1db53a9 to get more accurate results

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files
@@ Coverage Diff @@## main #2436 +/- ##
==========================================
+ Coverage 90.24% 90.96% +0.71% 
==========================================
Files 106 106 Lines 55774 62618 +6844 Branches 55774 62618 +6844 ==========================================
+ Hits 50335 56959 +6624 - Misses 5439 5659 +220 
Impacted FilesCoverage Δ
lightning/src/routing/router.rs93.51% <100.00%> (+0.16%)⬆️

... and 10 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Comment threadlightning/src/routing/router.rs Outdated
Comment threadlightning/src/routing/router.rs Outdated
Comment on lines -1721 to +1761
if !contributes_sufficient_value || exceeds_max_path_length ||
exceeds_cltv_delta_limit || payment_failed_on_this_channel {
// Path isn't useful, ignore it and move on.
if !contributes_sufficient_value {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to insufficient value contribution.", LoggedCandidateHop(&$candidate));
}
num_ignored_value_contribution += 1;
} else if exceeds_max_path_length {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding max. path length limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_path_length_limit += 1;
} else if exceeds_cltv_delta_limit {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding CLTV delta limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_cltv_delta_limit += 1;
} else if payment_failed_on_this_channel {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to a failed previous payment attempt.", LoggedCandidateHop(&$candidate));
}
num_ignored_previously_failed += 1;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

@valentinewallacevalentinewallaceJul 21, 2023

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

True, might be best to just have one long log that includes all the variables, which would remove all the branching as well

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

Not necessarily, but we log and count the first reason why a candidate would be excluded. Yes, some should count towards multiple categories, but it's probably not worth to check for all combinations.

True, might be best to just have one long log that includes all the variables

Mh, I think even if some candidates might fall under multiple categories, it's much more readable to have individual logs?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think its useful to have individual reasons why a particular candidate was ignored.

@jkczyzjkczyz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM. Please squash

tnull added 2 commits July 21, 2023 20:28
As `RouteParameters` are not included anymore in
`Event::PaymentPathFailed` since 0.0.115, and we don't give value/payee
as immediate arguments to `find_route` anymore.
Previously, we barely gave any hints why we excluded certain hops during
pathfinding. Here, we introduce more verbose logging by a) accounting
how much candidates we ignored for which reasons and b) logging any
first/last/blinded hops we end up ignoring.
Fixeslightningdevkit#1646.
@tnull
tnullforce-pushed the 2023-07-improve-router-logging branch from fd94350 to 1db53a9CompareJuly 21, 2023 18:28
@tnull

Copy link
Copy Markdown
ContributorAuthor

LGTM. Please squash

Squashed without further changes.

@jkczyz
jkczyz merged commit 0fadb54 into lightningdevkit:mainJul 21, 2023
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve logging of pathfinding behavior

6 participants

@tnull@codecov-commenter@TheBlueMatt@G8XSU@jkczyz@valentinewallace
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

Improve router logging and update documentation - #2436

Merged
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging
Jul 21, 2023
Merged

Improve router logging and update documentation#2436
jkczyz merged 2 commits into
lightningdevkit:mainfrom
tnull:2023-07-improve-router-logging

Conversation

@tnull

@tnulltnull commented Jul 21, 2023

Copy link
Copy Markdown
Contributor

Fixes#1646

As #2417 will slip to a future release, this PR just includes the improved logging and documentation fixups of of our router.

Previously, we barely gave any hints why we excluded certain hops during pathfinding. Here, we introduce more verbose logging by a) accounting how much candidates we ignored for which reasons and b) logging any first/last/blinded hops we end up ignoring.

We also improve documentation as RouteParameters are not included in Event::PaymentPathFailed since 0.0.115, and we don't give value/payee as immediate arguments to find_route anymore.

@tnull

Copy link
Copy Markdown
ContributorAuthor

Just to carry over some of the context here, the benches from #2417 with n = 10000 (on Linux on Intel(R) Xeon(R) CPU E3-1226 v3 @ 3.30GHz) interestingly indicate the logging changes actually maintain or even improve the pathfinding performance:

Benchmarking generate_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1208.3 s (10k iterations)
Benchmarking generate_routes_with_zero_penalty_scorer: Analyzing
generate_routes_with_zero_penalty_scorer
time: [118.83 ms 119.77 ms 120.71 ms]
change: [-1.7780% -0.4836% +0.7940%] (p = 0.45 > 0.05)
No change in performance detected.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Collecting 10000 samples in estimated 1139.0 s (10k iterations)
Benchmarking generate_mpp_routes_with_zero_penalty_scorer: Analyzing
generate_mpp_routes_with_zero_penalty_scorer
time: [110.90 ms 111.74 ms 112.58 ms]
change: [-11.985% -10.971% -9.9144%] (p = 0.00 < 0.05)
Performance has improved.
Found 400 outliers among 10000 measurements (4.00%)
400 (4.00%) high mild
Benchmarking generate_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1587.6 s (10k iterations)
Benchmarking generate_routes_with_probabilistic_scorer: Analyzing
generate_routes_with_probabilistic_scorer
time: [158.24 ms 158.62 ms 159.00 ms]
change: [-2.6897% -2.4127% -2.1132%] (p = 0.00 < 0.05)
Performance has improved.
Found 183 outliers among 10000 measurements (1.83%)
183 (1.83%) low mild
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 1552.4 s (10k iterations)
Benchmarking generate_mpp_routes_with_probabilistic_scorer: Analyzing
generate_mpp_routes_with_probabilistic_scorer
time: [156.10 ms 156.53 ms 156.96 ms]
change: [-1.8478% -1.4928% -1.1282%] (p = 0.00 < 0.05)
Performance has improved.
Found 200 outliers among 10000 measurements (2.00%)
200 (2.00%) high mild
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Collecting 10000 samples in estimated 3672.8 s (10k iterations)
Benchmarking generate_large_mpp_routes_with_probabilistic_scorer: Analyzing
generate_large_mpp_routes_with_probabilistic_scorer
time: [349.39 ms 354.79 ms 360.26 ms]
change: [-15.815% -14.168% -12.477%] (p = 0.00 < 0.05)
Performance has improved.
Found 1400 outliers among 10000 measurements (14.00%)
802 (8.02%) high mild
598 (5.98%) high severe

@tnulltnull added this to the 0.0.116 milestone Jul 21, 2023
@codecov-commenter

codecov-commenter commented Jul 21, 2023

Copy link
Copy Markdown

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.71 🎉

Comparison is base (e4c44f3) 90.24% compared to head (14f5544) 90.96%.

❗ Current head 14f5544 differs from pull request most recent head 1db53a9. Consider uploading reports for the commit 1db53a9 to get more accurate results

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files
@@ Coverage Diff @@## main #2436 +/- ##
==========================================
+ Coverage 90.24% 90.96% +0.71% 
==========================================
Files 106 106 Lines 55774 62618 +6844 Branches 55774 62618 +6844 ==========================================
+ Hits 50335 56959 +6624 - Misses 5439 5659 +220 
Impacted FilesCoverage Δ
lightning/src/routing/router.rs93.51% <100.00%> (+0.16%)⬆️

... and 10 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

Comment threadlightning/src/routing/router.rs Outdated
Comment threadlightning/src/routing/router.rs Outdated
Comment on lines -1721 to +1761
if !contributes_sufficient_value || exceeds_max_path_length ||
exceeds_cltv_delta_limit || payment_failed_on_this_channel {
// Path isn't useful, ignore it and move on.
if !contributes_sufficient_value {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to insufficient value contribution.", LoggedCandidateHop(&$candidate));
}
num_ignored_value_contribution += 1;
} else if exceeds_max_path_length {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding max. path length limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_path_length_limit += 1;
} else if exceeds_cltv_delta_limit {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to exceeding CLTV delta limit.", LoggedCandidateHop(&$candidate));
}
num_ignored_cltv_delta_limit += 1;
} else if payment_failed_on_this_channel {
if should_log_candidate {
log_trace!(logger, "Ignoring {} due to a failed previous payment attempt.", LoggedCandidateHop(&$candidate));
}
num_ignored_previously_failed += 1;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

@valentinewallacevalentinewallaceJul 21, 2023

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

True, might be best to just have one long log that includes all the variables, which would remove all the branching as well

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Are these actually mutually exclusive?

Not necessarily, but we log and count the first reason why a candidate would be excluded. Yes, some should count towards multiple categories, but it's probably not worth to check for all combinations.

True, might be best to just have one long log that includes all the variables

Mh, I think even if some candidates might fall under multiple categories, it's much more readable to have individual logs?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think its useful to have individual reasons why a particular candidate was ignored.

@jkczyzjkczyz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM. Please squash

tnull added 2 commits July 21, 2023 20:28
As `RouteParameters` are not included anymore in
`Event::PaymentPathFailed` since 0.0.115, and we don't give value/payee
as immediate arguments to `find_route` anymore.
Previously, we barely gave any hints why we excluded certain hops during
pathfinding. Here, we introduce more verbose logging by a) accounting
how much candidates we ignored for which reasons and b) logging any
first/last/blinded hops we end up ignoring.
Fixeslightningdevkit#1646.
@tnull
tnullforce-pushed the 2023-07-improve-router-logging branch from fd94350 to 1db53a9CompareJuly 21, 2023 18:28
@tnull

Copy link
Copy Markdown
ContributorAuthor

LGTM. Please squash

Squashed without further changes.

@jkczyz
jkczyz merged commit 0fadb54 into lightningdevkit:mainJul 21, 2023
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve logging of pathfinding behavior

6 participants

@tnull@codecov-commenter@TheBlueMatt@G8XSU@jkczyz@valentinewallace