Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Transactions is never included on the next block #1327

Closed
xlc opened this issue Aug 31, 2023 · 4 comments
Closed

Transactions is never included on the next block #1327

xlc opened this issue Aug 31, 2023 · 4 comments

Comments

@xlc
Copy link
Contributor

xlc commented Aug 31, 2023

Our team have observed that on most, if not all, parachains, transaction confirmation time is never less than 12s. i.e. They are never included on the next block.

I did 30 transfers on the asset hub rococo and this is the result

2023-08-31T04:57:28.745Z :  Avg 20.31816666666667 s
2023-08-31T04:57:28.745Z :  Min 13.763 s
2023-08-31T04:57:28.745Z :  Max 30.589 s

Is there something can be done to improve this? I know async backing can help, but still want to know what if there is a bottleneck that can be fixed

Related issues:
AcalaNetwork/Acala#2527
moonbeam-foundation/moonbeam#2286
@seunlanlege
Copy link
Contributor

seunlanlege commented Aug 31, 2023 •
edited
Loading

Do you think this has anything to do with extrinsic mortality?

@xlc
Copy link
Contributor Author

xlc commented Aug 31, 2023

I don’t think so. This can also be observed on Moonbeam with EVM transactions, which I don’t think have mortality.

@bkchr
Copy link
Member

bkchr commented Aug 31, 2023

I think the issue is this: #1202

One of the problems is that it actually reports inclusion way too late. Not sure about the direct inclusion, but this could also be influenced by this.

serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
@svyatonik @serban300
Using-same-fork metric for finality and complex relay (paritytech#1327)
6c49a91 
* using_same_fork metric in finality relay

* support `using_different_forks` in messages relay

* added dashboards and alerts

* lockfile
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
@svyatonik @serban300
Using-same-fork metric for finality and complex relay (paritytech#1327)
7d2029d 
* using_same_fork metric in finality relay

* support `using_different_forks` in messages relay

* added dashboards and alerts

* lockfile
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
@svyatonik @serban300
Using-same-fork metric for finality and complex relay (paritytech#1327)
b54d267 
* using_same_fork metric in finality relay

* support `using_different_forks` in messages relay

* added dashboards and alerts

* lockfile
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
@svyatonik @serban300
Using-same-fork metric for finality and complex relay (paritytech#1327)
0e0f1b2 
* using_same_fork metric in finality relay

* support `using_different_forks` in messages relay

* added dashboards and alerts

* lockfile
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
@svyatonik @serban300
Using-same-fork metric for finality and complex relay (paritytech#1327)
3994b98 
* using_same_fork metric in finality relay

* support `using_different_forks` in messages relay

* added dashboards and alerts

* lockfile
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
@svyatonik @serban300
Using-same-fork metric for finality and complex relay (paritytech#1327)
2025c79 
* using_same_fork metric in finality relay

* support `using_different_forks` in messages relay

* added dashboards and alerts

* lockfile
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
@svyatonik @serban300
Using-same-fork metric for finality and complex relay (paritytech#1327)
fba27d7 
* using_same_fork metric in finality relay

* support `using_different_forks` in messages relay

* added dashboards and alerts

* lockfile
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
@svyatonik @serban300
Using-same-fork metric for finality and complex relay (paritytech#1327)
691858a 
* using_same_fork metric in finality relay

* support `using_different_forks` in messages relay

* added dashboards and alerts

* lockfile
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
@svyatonik @serban300
Using-same-fork metric for finality and complex relay (paritytech#1327)
ac3a1ed 
* using_same_fork metric in finality relay

* support `using_different_forks` in messages relay

* added dashboards and alerts

* lockfile
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
@svyatonik @serban300
Using-same-fork metric for finality and complex relay (paritytech#1327)
28d99f0 
* using_same_fork metric in finality relay

* support `using_different_forks` in messages relay

* added dashboards and alerts

* lockfile
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 10, 2024
@svyatonik @serban300
Using-same-fork metric for finality and complex relay (paritytech#1327)
ef00ea3 
* using_same_fork metric in finality relay

* support `using_different_forks` in messages relay

* added dashboards and alerts

* lockfile
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 10, 2024
@svyatonik @serban300
Using-same-fork metric for finality and complex relay (paritytech#1327)
1b1cc3e 
* using_same_fork metric in finality relay

* support `using_different_forks` in messages relay

* added dashboards and alerts

* lockfile
bkchr pushed a commit that referenced this issue Apr 10, 2024
@svyatonik @bkchr
Using-same-fork metric for finality and complex relay (#1327)
e29b590 
* using_same_fork metric in finality relay

* support `using_different_forks` in messages relay

* added dashboards and alerts

* lockfile
@bkchr
Copy link
Member

bkchr commented Apr 22, 2024

Should be fixed by: b25d29a

@bkchr bkchr closed this as completed Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@xlc @bkchr @seunlanlege