paritytech / paritytech/subxt

Is our lightclient slower than PAPIs? Let's check!

Open
#1,911 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

solution-engineer
Dominant language
Rust
Stars
489
Forks
293
Avg merge
18h 35m
Merged PRs (30d)
3

Description

This comment came up on our Matrix Subxt Lounge room:

I played a bit last year with yew and subxt using the light-client feature, end up doing this small dapp https://www.goclaimit.app/?chain=polkadot&lc=true

Compared to PAPI, the app takes much more time to initiate the smoldot client before it can be used to fetch data example https://bounties.usepapi.app/

Let's check this; we both use Smoldot so I can't see a good reason why one would be any different from the other here.

One way to check this is to make a Small Subxt example using the lightclient to do something, and make the same example in PAPI, and then time how long they both take. if there's an obvious difference then we'd need to work out which part of the script is taking the time and why.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by making the Small Subxt light-client example described in the issue and an equivalent PAPI example, then time how long each takes to initialize before fetching data. Compare the results and identify which part of the script accounts for any obvious difference; done means the performance difference and likely source are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.